Integrated security system

ABSTRACT

A security system is provided to integrate a local existing security system with other security and automation devices which may not be compatible with the existing security system. The security system can connect and integrate an existing security system, and provide a centralized point of controlling all existing and new security and automation devices in a premise, thereby allowing flexibility in modifying and expanding a security system in the premise without need of replacing the security system that has been already installed throughout the premise. The security system can at least partially self-program to communicate with an existing security system when the security system is connected to the existing security system.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a National Stage Application under 35 U.S.C. § 371of International Application No. PCT/US2020/026934, filed on Apr. 6,2020, which claims priority to U.S. Provisional Patent Application Ser.Nos. 62/830,359, filed on Apr. 5, 2019, 62/874,480, filed on Jul. 15,2019, 62/874,230, filed Jul. 15, 2019, 62/874,256, filed Jul. 15, 2019,62/874,270, filed Jul. 15, 2019, and 62/874,283, filed Jul. 15, 2019.This disclosure of the prior applications is considered part of thedisclosure of this application, and is incorporated in its entirety intothis application.

TECHNICAL FIELD

This document describes devices, systems, and methods related to homesecurity.

BACKGROUND

Home security systems have included a control panel that managescommunications with devices, such as door and window sensors, locks,alarms, lighting, motion detectors, security cameras, etc., throughoutthe house using particular communication protocols. The control panelmay communicate with one or more remote devices or central stationsusing particular communication protocols.

Home automation is building automation for a home, called a smart homeor smart house. A home automation system will control lighting, climate,entertainment systems, and appliances. It may also include home securitysuch as access control and alarm systems. Devices in such homeautomation can be connected with the Internet. For example, a homeautomation system may connect controlled devices to a central hub orgateway. The user interface for control of the system uses eitherwall-mounted terminals, tablet or desktop computers, a mobile phoneapplication, or a Web interface, that may also be accessible off-sitethrough the Internet.

For a variety of reasons, it is often desirable to upgrade an existingsecurity system to include additional or different forms of protection.This may be the case if, for example, a facility (for example, a home,commercial facility, etc.) has expanded in size, the system in place hassome features that are undesirable for the facility owner or operator,or the facility owner or operator wishes to have a different monitoringcompany in charge of the facility (for example, a monitoring companythat charges a lower monthly fee), and that monitoring company requiresa particular system control device with which to communicate. In such acase, it may be desirable to switch the existing system control deviceto a control device that has some advantage that is valuable to thefacility owner or operator. However, an existing system control deviceand a new control device may be only able to detect and receivetransmissions from sensors that have particular data packet protocolsand definitional parameters that are specifically designed to work withthe existing system control device and the new control device,respectively. That said, it is also not desirable to have to discardentirely an entire existing security system simply to migrate to adifferent system control device.

SUMMARY

Some embodiments described herein include a home security system thatintegrates a local existing security system with other security andautomation devices which may not be compatible with the existingsecurity system. For example, an existing security system, which hasbeen used for a while, may be outdated with limited capabilities (e.g.,a security alarm functionality only) and without support of additionalfunctionalities to meet changing security environments in a premise.Some embodiments of the home security system described herein areconfigured to connect and integrate such an existing security system,and provide a centralized point of controlling all existing and newsecurity and automation devices in a premise. This allows flexibility inmodifying and expanding a security system in the premise without need ofreplacing the security system that has been already installed throughoutthe premise.

In some examples, a home security system provides a cloud-based securityintegration system configured to integrate a local security system withother security and automation devices that exist in parallel with thelocal security system or are later added in a premise. The integrationsystem can include a security cloud server and a security communicatordevice that communicates with the security cloud server. The securitycommunicator device can be in the form of a security panel.

Some embodiments of the security communicator device can be configuredto connect with an existing home security system to upgrade or“takeover” the existing home security system, such as to enhance thesystem with one or more additional features. For example, the securitycommunicator device can be wired to a control panel (e.g., a keypad) ofthe existing home security system to tap a data bus and/or telephonelines of the existing local security system. In addition, the securitycommunicator device includes a communication interface (e.g., a localarea network (LAN) interface) configured to communicate with one or moresecurity and automation components at the premise.

The security communicator device can include a communication interfaceconfigured to communicate with a security cloud server. In someimplementations, the security communicator device can include aplurality of communication interfaces that can be selectively used toconnect to the security cloud server or other remote computing devices.The plurality of communication interfaces can include interfaces for oneor more broadband protocols (e.g., Ethernet, Wi-Fi, and other suitablewired or wireless network protocols) and a cellular network of one ormore protocols (e.g., CDMA, TDMA, GSM, etc.). The security communicatordevice can be configured to select one of the plurality of communicationinterfaces based on one or more factors, such as availability, quality,speed, cost of utilizing communication paths, and other requirements. Inaddition or alternatively, the security communicator device can beconfigured to select communication path priorities through preferencesestablished in a network services platform. In some implementations, thesecurity communicator device is configured to automatically switch to anavailable communication path to maintain connection to the securitycloud server for intended functionalities (e.g., alarm reporting).

Some embodiments of the home security system can include one or moreuser controllers that are remote and connected to the securitycommunicator device. The user controllers provide a user interface for auser to interact with the home security system including, for example,the existing local security system, the security communicator device,the security cloud server, and other security and automation devicesconnected to the existing local security system, the securitycommunicator device, and/or the security cloud server. For example, theuser controllers can include a touch screen that displays informationabout the home security system and provides control elements (e.g., GUIbuttons) to receive user inputs.

Some embodiments of the security communicator device can be connected toadditional security devices, such as video cameras, sensors, and homeautomation devices, user's mobile devices, and a central station. Thesecurity communicator device can collect data from the existing localsecurity system, as well as data from other connected devices, andtransmit them to the security cloud server so that the security cloudserver can provide integrated security service.

Some embodiments of the security communicator device can at leastpartially self-program to communicate with an existing panel in theexisting security platform when the security communicator device isconnected to the existing panel. For example, when an installer connectsa security communicator device to an existing panel at the premises, thesecurity communicator device can automatically detect a type (e.g., aprotocol) of the existing panel, and adapt itself to permit forcommunication with the existing panel to take over at least partiallythe features and functionalities of the existing panel. Such automaticdetection and configuration may facilitate installation with theexisting security platform without complicating setups andconfigurations.

Particular embodiments described herein include a device for enhancing asecurity system for a premises that includes a security control panellocated at the premises. The device may include data bus terminal, ringand tip terminal, a communications interface, and a controller. The databus terminal are configured to be wired to a data bus of the securitycontrol panel. The security control panel receives and transmits signalsover the data bus related to security system. The security control panelcan be communicatively connected to and receive information on sensedconditions in or around the premises from security sensors positioned atthe premises. The ring and tip terminal is configured to be wired to atelephone line from the security control panel. The security controlpanel is configured to use the telephone line to report security alarmsto a remote central monitoring system. The communications interface isconfigured to be connected to one or more devices or systems that arenot supported directly by the security control panel. The controller isconfigured to enhance the security system for the premises by, at least,(i) obtaining security information from the security control panel viathe data bus terminals and the ring and tip terminals and (ii)augmenting the security information with additional security informationreceived from the one or more devices or systems over the communicationsinterface.

In some implementations, the system can optionally include one or moreof the following features.

The one or more devices or systems may include a remote server systemthat, in part, provides enhanced security features for the securitysystem. The communications interface may provide communication with theremote server system. The communications interface may include awireless communication interface through which the controllercommunicates with the remote server system over one or more wirelesscommunication channels. The wireless communication interface may includea cellular communication interface and the one or more wirelesscommunication channels include a cellular communication network. Thecellular communication networks may include a mobile data network. Thewireless communication interface may include a Wi-Fi communicationinterface and the one or more wireless communication channels include aWi-Fi network. The wireless communication interface may include aBluetooth communication interface and the one or more wirelesscommunication channels include a Bluetooth network. The communicationsinterface may include a wired communication interface through which thecontroller communicates with the remote server system over one or morewired communication channels. The wired communication interface mayinclude an Ethernet interface and the one or more wired communicationchannels include a local Ethernet network.

In some implementations, the security control panel does not includecommunication components capable of communicating with the remote serversystem or communicating with the remote central monitoring system beyondthe telephone line.

A connection between the security control panel and the remote centralmonitoring system may be severed by the telephone line of the securitycontrol panel being connected to the ring and tip terminals. The remoteserver system may be communicatively connected to the remote centralmonitoring system and configured to determine whether to transmitsecurity alarms to the remote central monitoring system based on thesecurity information and the additional security information.

In some implementations, the security control panel does not includeadditional interfaces for communicating with the remote centralmonitoring system beyond the telephone line.

The one or more devices or systems may include wireless sensors that aredifferent from the security sensors. The communications interface mayinclude a wireless sensor interface that is configured to communicatewith wireless sensors that are located in or around the premises. Theadditional information may include additional sensed conditions for thepremises as sensed by the wireless sensors. In some implementations, thesecurity control panel does not support direct enrollment of at least aportion of the wireless sensors. The controller may further beconfigured to enroll at least one of the wireless sensors with thesecurity control panel via an selected protocol translation layer fortranslating between protocols used by the at least one of the wirelesssensors and the security control panel.

The controller may be further configured to automatically detect acommunication protocol used by the security control panel and toautomatically configure communication with the security control panel byanalyzing signals transmitted over the data bus terminal and the ringand tip terminal. Automatically configuring may include enrolling thedevice with the security panel using the detected communicationprotocol. Automatic detection of the communication protocol may includedetecting the signals transmitted by the security panel, analyzing thesignals to detect one or more aspects of the signal, and selecting thecommunication protocol from among a plurality of communication protocolsbased on the aspects of the signals. The aspects of the signal mayinclude one or more of modulation types, frequency shifts, differentialsignals, data rates, data pack lengths, error checking, ports beingused, and/or other suitable physical and/or logical aspects of data inthe signal. The communication protocol used by the security controlpanel may be detected, at least in part, by transmitting one or moretest signals over the data bus and identifying response signals, or theabsence thereof, received from the security control panel. Thecommunication protocol used by the security control panel may bedetected, at least in part, by simulating a telephone service over ringand tip terminal and detecting a telephone protocol used by the securitycontrol panel over the telephone line. The telephone protocol may beselected from among a group of potential telephone protocols, includingControl ID, SIA, and 4/2.

The one or more devices or systems may include a wireless user interfacedevice that provides a user interface on premises for the securitysystem. The communications interface may include a wirelesscommunication interface that is configured to wirelessly communicatewith the wireless user interface device to provide status informationfor the security system and to receive user control commands for thesecurity system. The wireless user interface device may include awireless touchpad device that replaces a preexisting user interfacedevice that was connected to the security control panel. In someexamples, the preexisting user interface device had a wired connectionto the security control panel over the data bus that was disconnectedand replaced by the wired connection to the data bus terminal. Thestatus information may include the security information from thesecurity control panel and the additional security information receivedfrom other devices that are connected via the communication interface.Other devices may include wireless sensors that are enrolled via thecommunication interface and that are not capable of being enrolled withthe security control panel. The wireless user interface device mayinclude smartphone or tablet computing device running an applicationspecially programmed for wireless communication with the device via thecommunication interface.

In some implementations, the security control panel may be a preexistingsecurity control panel that has been installed at the premises. In someimplementations, the security sensors may be preexisting securitysensors that have been installed at the premise.

Some embodiments of the home security system can operate to blendinformation from an existing local security platform (e.g., a legacysystem or legacy system alarms) with other inputs from sensors anddevices that are added to the home security system (e.g., sensors anddevices connected directly to the security communicator device), and,based on the blended information, provide for integrated control ofsecurity and automation devices at premises where the existing localsecurity platform is located.

For example, the security communicator device can tap signals (e.g.,sensor status signals, alarm signals, etc.) from the existing localsecurity platform (e.g., the existing security control device). Inaddition, the security communicator device can receive inputs (e.g.,sensor status, trouble indication, low battery, alarms, etc.) from theperipheral devices (e.g., existing and new sensors and devices)connected to the security communicator device. A security cloud serverthat communicates with the security communicator device can blend thesignals from the existing local security platform and the inputs fromthe peripheral devices of the security communicator device, anddetermine one or more appropriate actions to be performed by thesecurity cloud server, the security communicator device, the existinglocal security platform, and/or other devices, systems, or entities.Such blended information is used to permit for integrated andcentralized control of all security and automation devices at thepremises.

Further, the home security system can operate to select from amongmultiple different communication channels to establish communicationbetween a security communicator device and a cloud computing system. Forexample, the security communicator device can selectively use one ofdifferent types of data communications with the security cloud server,such as broadband (Ethernet and Wi-Fi) and cellular. By way of example,such multiple options can be prioritized based on, for example, the typeof data being transmitted. For example, a video stream can be attemptedto be sent over broadband first and, if the broadband is not available,then over cellular.

Particular embodiments described herein include a system for providingintegrated security control. The system may include a security cloudserver, and a security communicator device. The security communicatordevice is configured to communicate with the security cloud server viaone or more networks. The security communicator device is configured tobe connected to an existing security panel at a premises and furtherconfigured to perform operations including receiving a signal from theexisting security panel, the signal representative of an existing deviceconnected to the existing security panel; transmitting the signal to thesecurity cloud server; receiving a peripheral device signalrepresentative of a peripheral device connected to the securitycommunicator device; transmitting the peripheral device signal to thesecurity cloud server; receiving a control signal from the securitycloud server, the control signal representative of a security actiondetermined based on the signal and the peripheral device signal; andcontrolling the existing security panel using the control signal.

In some implementations, the system can optionally include one or moreof the following features. Controlling the existing security panel mayinclude transmitting the control signal to the existing security panel.The control signal may be usable by the existing security panel tocontrol the existing device. The operations may include controlling theperipheral device based on the control signal. The security action maybe determined using security control rules. The security control rulesmay include a list of actions to be taken based on differentcombinations between possible statuses of the existing device andpossible statuses of the peripheral device. The operations may includeconverting the signal to a modified signal, the modified signalconfigured to be compatible with a protocol of the security communicatordevice. The operations may include converting the control signal to amodified control signal. The modified control signal may be configuredto be compatible with a protocol of the existing security panel. Theexisting security panel may be communicatively disconnected from acentral monitoring station. The existing device and the peripheraldevice may be arranged in a security zone being independently monitoredand controlled. The security communicator device may be connected to oneof data bus and/or telephone line of the existing security panel. Thenetworks may include one or more of an Ethernet communication, awireless communication, and a cellular communication.

Particular embodiments described herein include a security communicator.The security communicator may include a data processing apparatus, and amemory device storing instructions that when executed by the dataprocessing apparatus cause the server to perform operations comprising:receiving a signal from an existing security panel, the signalrepresentative of an existing device connected to the existing securitypanel; transmitting the signal to a security cloud server; receiving aperipheral device signal representative of a peripheral device connectedto the security communicator device; transmitting the peripheral devicesignal to the security cloud server; receiving a control signal from thesecurity cloud server, the control signal representative of a securityaction determined based on the signal and the peripheral device signal;and controlling the existing security panel using the control signal.

In some implementations, the system can optionally include one or moreof the following features. Controlling the existing security panel mayinclude transmitting the control signal to the existing security panel.The control signal may be usable by the existing security panel tocontrol the existing device. The operations may include controlling theperipheral device based on the control signal. The security action maybe determined using security control rules. The security control rulesmay include a list of actions to be taken based on differentcombinations between possible statuses of the existing device andpossible statuses of the peripheral device. The operations may includeconverting the signal to a modified signal. The modified signal may beconfigured to be compatible with a protocol of the security communicatordevice. The operations may include converting the control signal to amodified control signal. The modified control signal may be configuredto be compatible with a protocol of the existing security panel. Theexisting security panel may be communicatively disconnected from acentral monitoring station. The existing device and the peripheraldevice may be arranged in a security zone being independently monitoredand controlled.

Some embodiments of the home security system can permit for security andautomation devices (e.g., cameras, sensors, etc.) in the system to beremotely set up and configured through a security integration system,such as the security communicator device and/or the security cloudserver, instead of being set up and configured directly through acommunication network (e.g., a home router). Further, local changes tothe communication network environment at a premises, such as changinginternet providers and credentials, can be provisioned and updated onthe security and automation devices through the security integrationsystem at the premises. For example, security and automation devices ina home security system can be connected to a security communicatordevice, and set up and configured through the security communicatordevice that integrates an existing local security system and isconnected to a security cloud server. Alternatively or in addition,security and automation devices in a home security system can be set upand configured through a user controller and/or a mobile computingdevice that communicates with the security communicator device and/orthe security cloud server.

Particular embodiments described herein include a system for remotelyconfiguring a security device. The system may include a security cloudserver, a local network access device, and a security communicatordevice. The security communicator device is configured to communicatewith the security cloud server via one or more networks. The securitycommunicator device is configured to perform operations includingconnecting to the security device; receiving local network accessinformation from the security cloud server; and transmitting the localnetwork access information to the security device. The local networkaccess information may be usable to configure the security device toconnect to the local network access device.

In some implementations, the system can optionally include one or moreof the following features. The operations may include storing the localnetwork access information locally. The operations may includetransmitting to the security cloud server a request for the localnetwork access information. The operations may include transmitting tothe security cloud server a request for updated local network accessinformation; receiving the updated local network access information; andtransmitting the updated local network access information to thesecurity device. The operations may include, prior to the transmittingto the security cloud server a request for updated local network accessinformation, determining that the security device is disconnected fromthe local network access device. The operations may include receiving adevice identifier from the security device. The request may include thedevice identifier. The local network access information may bedetermined based on the device identifier. The security device may beconnected to the security communicator device in a roaming state. Thesecurity device may be a peripheral device connected to the securitycommunicator device. The security device may be an existing deviceconnected to an existing security panel. The existing security panel maybe connected to the security communicator device. The operations mayinclude receiving a signal from the existing security panel, the signalrepresentative of the existing device connected to the existing securitypanel; transmitting the signal to the security cloud server; receiving acontrol signal from the security cloud server, the control signalrepresentative of a security action determined based at least part onthe signal; and controlling the existing security panel using thecontrol signal. The security communicator device may be connected to oneof data bus and/or telephone line of the existing security panel. Thenetworks may include one or more of an Ethernet communication, awireless communication, and a cellular communication.

Particular embodiments described herein include a security communicator.The security communicator may include a data processing apparatus, and amemory device storing instructions that when executed by the dataprocessing apparatus cause the security communicator to performoperations including connecting to a security device; receiving localnetwork access information from a security cloud server; andtransmitting the local network access information to the securitydevice, the local network access information usable to configure thesecurity device to connect to a local network access device.

In some implementations, the system can optionally include one or moreof the following features. The operations may include storing the localnetwork access information locally. The operations may includetransmitting to the security cloud server a request for the localnetwork access information. The operations may include transmitting tothe security cloud server a request for updated local network accessinformation; receiving the updated local network access information; andtransmitting the updated local network access information to thesecurity device. The operations may include, prior to the transmittingto the security cloud server a request for updated local network accessinformation, determining that the security device is disconnected fromthe local network access device. The operations may include receiving adevice identifier from the security device. The request may include thedevice identifier. The local network access information may bedetermined based on the device identifier. The security device may beconnected to the security communicator in a roaming state. The securitydevice may be a peripheral device connected to the securitycommunicator, or an existing device connected to an existing securitypanel. The existing security panel may be connected to the securitycommunicator device.

Some embodiments of a home security system described herein allowremotely provisioning and configuring security and automation devicesthrough a security integration system, such as a security communicatordevice which is connected to a security cloud server, instead of beingconnected directly through a network router. This enables security andautomation devices to automatically connect to a network and maintainthe connection without manually reconfiguring the devices whenconnection settings are modified, such as changes to network routersetups (e.g., changing internet providers or credentials). The automatednetwork connection allows easy setup and configuration of devices in ahome security system and provide flexibility in expanding the homesecurity system.

Some embodiments of the home security system can selectively choosemultiple routes for signals (e.g., data streams) from security andautomation devices to different devices such as output devices. Forexample, the home security system can select one of multiple routes fora video stream from a camera to a display device (e.g., a touchpad) fordisplay. Multiple different pathways can be selectively used, such as apathway through a remote security cloud server and another local pathwaythrough the device itself.

Further, some embodiments of the home security system can operate toselect from among multiple different communication channels to establishcommunication between a security communicator device and a cloudcomputing system. For example, the security communicator device canselectively use one of different types of data communications with thesecurity cloud server, such as broadband (Ethernet and Wi-Fi) andcellular. By way of example, such multiple options can be prioritizedbased on, for example, the type of data being transmitted. In oneexample, a video stream can be attempted to be sent over broadband firstand, if the broadband is not available, then over cellular. In anotherexample, the system is configured to permit for a video stream to besent over broadband only, but not over cellular.

Particular embodiments described herein include a system for providingintegrated security control. The system may include an existing securitypanel, a security cloud server, a local network access device, an outputdevice, and a security communicator device. The security communicatordevice is configured to be connected to the existing security panel. Thesecurity communicator device includes a plurality of communicationinterfaces and is configured to select one of the plurality ofcommunication interfaces to communicate with the security cloud server.The security communicator device is configured to perform operationsincluding: connecting to the existing security panel; receiving a devicesignal from a security device associated with the security communicatordevice; transmitting the device signal to the security cloud serverusing the one of the plurality of communication interfaces, the securitycloud server configured to process the device signal and generate aprocessed signal; receiving the processed signal from the security cloudserver using the one of the plurality of communication interfaces; andpermitting the processed signal to be transmitted to the output device,the output device configured to output content contained in theprocessed signal.

In some implementations, the system can optionally include one or moreof the following features. The output device may be connected to thesecurity communicator device through the local network access device.The processed signal may be routed to the output device through thelocal network access device. The output device may be connected directlyto the security communicator device. The processed signal may be routedto the output device through the security communicator device. Theplurality of communication interfaces may include an Ethernetcommunication interface, a wireless communication interface, and acellular communication interface. The operations may includeautomatically switching between the plurality of communicationinterfaces. The operations may include selecting communication pathpriorities among the plurality of communication interfaces throughpreferences established in a network services platform. The operationsmay include selecting, from among a plurality of communication paths, anoptimal communication path to be used by the security communicatordevice based on one or more of a plurality of factors. The plurality offactors may include costs associated with using the plurality ofcommunication paths. The plurality of factors may include currentavailability of the plurality of communication paths. The plurality offactors may include latency needs related to sensor data to betransmitted by the security communicator device. The plurality offactors may include sensor triggered criteria. The operations mayinclude receiving an existing device signal from an existing securitydevice through the existing security panel, the existing security devicebeing connected to the existing security panel; transmitting theexisting device signal to the security cloud server using the one of theplurality of communication interfaces, the security cloud serverconfigured to process the device signal and generating a secondprocessed signal; receiving the second processed signal from thesecurity cloud server using the one of the plurality of communicationinterfaces; and permitting the second processed signal to be transmittedto the output device, the output device configured to output contentcontained in the second processed signal. The operations may includetranslating the existing device signal to be compatible with a protocolof the security communicator device. The security communicator devicemay be connected to one of data bus and/or telephone line of theexisting security panel. The existing security panel may be disconnectedfrom an existing communication network when connected to the securitycommunicator device. The device signal may include media content, andwherein the device signal is transmitted from the security cloud serverto a media analysis server for analysis. The output device may include adisplay screen for displaying the content. The local network accessdevice may include a broadband router.

Some embodiments of the integrated security system include one or morecomputing devices with an integrated user interface for outputtingsecurity and automation information and receiving user inputs ofcontrolling the system. The user interface is configured to integrateoutputs from the existing local security platform and outputs from thesecurity communicator device and associated peripheral devices, andpresent a blend of information for the entire integrated securitysystem, thereby providing for integrated view and control of securityand automation devices at the premises. For example, the integrated userinterface can provide an all-in-one dashboard that displays both of thesecurity information from the existing security panel and theinformation from additional security and automation devices (e.g.,newly-added security sensors, cameras, home automation sensors, etc.).The integrated user interface permits for a user to access informationfrom both the existing security panel platform and the securitycommunicator device connected thereto, and provide a user control forthe entire system from the same user interface, without requiringseparate different credentials for logging in.

The computing devices with an integrated user interface can include oneor more user controllers dedicated to the security integration systemand connected to the security communicator device either directly or viaa local network access device. In addition or alternatively, thecomputing devices can include a user computing device (e.g., a user'smobile device) running a software application configured to provide theuser interface.

Particular embodiments described herein include a system for providingintegrated security control. The system includes a security cloudserver, a user control device, and a security communicator device. Thesecurity communicator device is configured to communicate with thesecurity cloud server via one or more networks. The securitycommunicator device is configured to be connected to an existingsecurity panel at a premises and further configured to performoperations comprising receiving a signal from the existing securitypanel, the signal representative of an existing device connected to theexisting security panel; transmitting the signal to the security cloudserver; receiving a peripheral device signal representative of aperipheral device connected to the security communicator device;transmitting the peripheral device signal to the security cloud server;receiving a control signal from the security cloud server, the controlsignal including information about a security action determined based onthe signal and the peripheral device signal; controlling the existingsecurity panel using the control signal; connecting to the user controldevice; and transmitting the control signal to the user control device,the control signal being usable to generate an integrated controlinterface at the user control device.

In some implementations, the system can optionally include one or moreof the following features. The operations may include receiving a userinput from the user control device, the user input received through theintegrated control interface. The integrated control interface mayinclude a blend of information about the existing device and informationabout the peripheral device. The user control device may be a portabledevice. The user control device may be connected to the securitycommunicator device through a local network access device. Controllingthe existing security panel may include transmitting the control signalto the existing security panel. The control signal may be usable by theexisting security panel to control the existing device. The operationsmay include controlling the peripheral device based on the controlsignal. The operations may include translating the signal to a modifiedsignal, the modified signal configured to be compatible with a protocolof the security communicator device. The operations may includeconverting the control signal to a modified control signal, the modifiedcontrol signal configured to be compatible with a protocol of theexisting security panel. The existing device and the peripheral devicemay be arranged in a security zone being independently monitored andcontrolled. The security communicator device may be connected to one ofdata bus and/or telephone line of the existing security panel. Thenetworks may include one or more of an Ethernet communication, awireless communication, and a cellular communication.

Particular embodiments described herein include a user control devicefor an integrated security system. The user control device may include adata processing apparatus, a display screen, and a memory device storinginstructions that when executed by the data processing apparatus causethe user control device to perform operations comprising: connecting toa security communicator device; receiving a control signal from thesecurity communicator device, the control signal being generated basedon a signal from an existing security panel connected to the securitycommunicator device, and based further on a peripheral device signalfrom a peripheral device connected to the security communicator device;and generating an integrated control interface using the display screen,the integrated control interface displaying a blend of information aboutthe existing security panel and information about the peripheral device.

In some implementations, the system can optionally include one or moreof the following features. The operations may include receiving a userinput through the integrated control interface. The user input may befor controlling the existing security panel or the peripheral device.The user control device may be a portable device. The user controldevice may be connected to the security communicator device through alocal network access device. The user control device may be paireddirectly with the security communicator device. An existing device andthe peripheral device may be arranged in a security zone beingindependently monitored and controlled. The existing device may beconnected to the existing security panel. The security communicatordevice may be configured to communicate with a security cloud server viaone or more networks, and further configured to perform operationsincluding: receiving the signal from the existing security panel, thesignal representative of an existing device connected to the existingsecurity panel; transmitting the signal to the security cloud server;receiving the peripheral device signal representative of a peripheraldevice connected to the security communicator device; transmitting theperipheral device signal to the security cloud server; receiving thecontrol signal from the security cloud server, the control signalincluding information about a security action determined based on thesignal and the peripheral device signal; and controlling the existingsecurity panel using the control signal. The security communicatordevice may be connected to one of data bus and/or telephone line of theexisting security panel.

Some embodiments described herein include a communicator device that canbe used to upgrade or “takeover” an existing home security system, suchas to enhance the system with one or more additional features. Forexample, some embodiments described herein include a system, comprisinga communicator device configured to connect with a legacy securitypanel, the communicator device including a wireless local networkcommunication interface configured to communicate wirelessly with one ormore components located at a premise, and a wireless remotecommunication interface.

Some embodiments described herein include a system, comprising a videocamera; a communicator device including a communication interfaceconfigured to communicate with a video camera device; and a displaydevice configured to receive video communication from the video cameravia the communicator device.

Some embodiments described herein include a communicator deviceconfigured to connect with a legacy security panel, comprising: aplurality of communication interfaces, including: an Ethernetcommunication interface, a wireless communication interface, and acellular communication interface. In some implementations, thecommunicator device is configured to select one of the plurality ofcommunication interfaces based on a cost of utilizing the communicationpath. In some implementations, the communicator device is configured toautomatically switch to an available communication path to maintainalarm reporting.

Some embodiments described herein include a communicator deviceconfigured to connect with a legacy security panel, comprising: atranslator configured to translate a proprietary encrypted securitysensor signal; wherein the communicator device is configured tocommunicate with proprietary encrypted security sensors using thetranslator.

Some embodiments described herein include a communicator deviceconfigured to facilitate local network connection configuration over acellular link such that a system connected with the communicator devicemay be remotely managed.

Some embodiments described herein include a system, comprising: acommunicator device configured to connect with a legacy security panel,the communicator device comprising: an Ethernet communication interface,a wireless communication interface, and a cellular communicationinterface; a translator configured to translate a proprietary encryptedsecurity sensor signal; a video camera; a display device configured toreceive video communication from the video camera via the communicatordevice. In some implementations, the communicator device is configuredto communicate with proprietary encrypted security sensors using thetranslator, and the communicator device is configured to automaticallyswitch to an available communication path to maintain alarm reporting.

Some embodiments described herein include a system comprising: acommunicator device configured to connect to a legacy security panel,the communicator device comprising: a sensor radio, and a communicationinterface; and a cloud platform configured to communicate with thecommunicator device over one or more networks via the communicatordevice's communication interface; wherein sensor enrollment is providedvia the sensor radio. In some implementations, the sensor enrollment iswith the legacy security panel via the sensor radio. In someimplementations, the sensor enrollment is with the cloud platform viathe sensor radio, and sensor enrollment with the cloud platform providesfor security monitoring independent of security monitoring provided bythe legacy security panel. In some implementations, the communicatordevice is configured to add sensors to be monitored without triggeringalarms on the legacy security system. In some implementations, thesensor enrollment is provided by both the legacy security panel and thecloud platform via the sensor radio.

Some embodiments described herein include a communicator deviceconfigured to self-configure itself to a separate security system by (i)sensing hardware connections with and signals transmitted with theseparate security system and (ii) making responsive configurations toenable system functionality.

Some embodiments described herein include a communicator deviceconfigured to select communication path priorities through preferencesestablished in a network services platform.

Some embodiments described herein include a communicator deviceconfigured to select, from among a plurality of communication paths, anoptimal communication path to be used by the communicator device basedon one or more of a plurality of factors. In some implementations, theplurality of factors include costs associated with using the pluralityof communication paths. In some implementations, the plurality offactors include current availability of the plurality of communicationpaths. In some implementations, the plurality of factors include latencyneeds related to sensor data to be transmitted by the communicatordevice. In some implementations, the plurality of factors include sensortriggered criteria.

Some embodiments described herein include a communicator deviceconfigured to automatically switch from cloud platform control to localcontrol based on detection by one of a plurality of local WANs providedby the communicator device.

The technologies described herein may provide one or more of thefollowing advantages. Some embodiments described herein include asecurity communicator device that is connectable to an existing securityplatform (e.g., a legacy security panel or keypad) and can furtherconnect to other security and home automation devices which are notcompatible with the existing security platform, thereby integrating allthe home security and automation devices. The security communicatordevice provides a centralized point of controlling all existing and newsecurity and automation devices at a premise, and allow flexibility inmodifying and expanding a security system at the premise without need ofreplacing the security system that has been already installed throughoutthe premise.

Some embodiments of the security communicator device can be controlledby one or more remote control devices, such as on-site user controllers,user mobile devices, and other remote computing devices, which can runsoftware applications providing the same or similar user interfaces sothat a user can see and interact with the same or similar userinterfaces regardless of the types of security platforms, systems,devices, and components being installed on the premise. A user caninterface with all security and automation devices in the same waythrough such remote control devices.

Some embodiments of the security communicator device, when connected toan existing security panel, is self-configured without an installer'sinput, to communicate with the existing security panel even if aprotocol used by the existing security panel is not compatible with aprotocol of the security communicator device. This can allow aninstaller to install a security communicator device to an existingsecurity panel without having to be specially trained in theidentification of the existing security panel and the setup of thesecurity communicator device against the existing security panel.

Some embodiments of a home security system described herein permit formultiple different pathways to be selectively chosen to route datastreams among different devices, such as from security and automationdevices to output devices, thereby ensuring continuous data transmissionbetween devices in reliable and cost-efficient manners.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features andadvantages will be apparent from the description and drawings, and fromthe claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an example system for integrated home security andautomation services.

FIG. 1B illustrates an example connection between a control panel and asecurity communicator device.

FIG. 1C is a diagram of an example environment that implements thesystem of FIG. 1A.

FIG. 2 is a flowchart of an example method for providing an integratedhome security and automation service by installing a securitycommunicator device at a premise

FIG. 3A is a diagram of an example security communicator deviceconfigured to provide an integrated home security and automation service

FIG. 3B is a diagram of an example circuit board of the securitycommunicator device.

FIG. 3C illustrates an example housing for a security communicatordevice.

FIG. 4 illustrates an example operation of an integrated security systemfor centralizing all home security and automation controls.

FIG. 5 illustrates an example technique for connecting a securityintegration system to an existing security platform.

FIG. 6A illustrates an example packet, or data, protocols that may beused by a security system.

FIG. 6B illustrates another example packet, or data, protocols that maybe used by a security system.

FIG. 7 is a flowchart of an example process for automaticallyconfiguring a security communicator device.

FIG. 8 illustrates an example technique for blending information from anexisting security platform with other inputs of a security integrationsystem.

FIGS. 9A-9B is a flowchart of an example method for providing integratedhome security and automation control based on a blend of inputs from alegacy security panel and a security communicator.

FIG. 10 illustrates example data that provide a list of actionsaccording to a blend of legacy data from a legacy security panel andadditional data from a security communicator.

FIG. 11A illustrates an example system for provisioning and/orconfiguring security devices through a security communicator device.

FIG. 11B illustrates an example system for provisioning and/orconfiguring security devices through a security communicator device.

FIG. 12 is a flowchart of an example method for automatic configurationof a security device against a local network access device.

FIG. 13 is a flowchart of an example method for automatic configurationof a security device 1202 against a local network access device.

FIGS. 14A-14D illustrate example pathways for routing data from asecurity device to an output device in the integrated home securitysystem.

FIGS. 15A-15B illustrate other example pathways for routing data from asecurity device to an output device in the integrated home securitysystem.

FIGS. 16A-16D illustrate yet other example pathways for routing datafrom a security device to an output device in the integrated homesecurity system.

FIG. 17 illustrates an example technique for blending information froman existing security platform with other inputs of a securityintegration system, and outputting a blend of information using outputdevices.

FIGS. 18A-18B illustrate example integrated control interfaces on outputdevices.

FIGS. 19A-19C illustrate example integrated control interfaces on outputdevices.

FIG. 20 is a schematic view of an example system including acommunicator device.

FIG. 21 depicts an example system within which the communicator deviceis configured to provide the services and features described throughoutthis document.

FIG. 22 is depicts an example system with a more detailed view of thecomponents of the communicator device.

FIG. 23 is a block diagram of computing devices that may be used toimplement the systems and methods described in this document, as eithera client or as a server or plurality of servers.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

A home security system provides a centralized point of controlling allexisting and new security and automation devices at a premise (e.g.,houses, buildings, or other facilities). The system involves at leastthree subsystems: an existing local security platform, a securitycommunicator device (e.g., a security panel and/or user controller(s)),and a security cloud server. A security communicator device can includea security panel that is installed in a premise and connected to theexisting local security platform in the premise. The security panel cancome with one or more user controllers (e.g., touchpads) that provide anintegrated user interface for a user to manage and control all securityand automation devices in one place. The security panel is operated totap a data bus of the existing local security platform to obtainsecurity data from the platform. Further, the security panel can receivedata from the other security and automation devices at the premise. Thesecurity data from the existing local security platform and the datafrom the other security and automation devices can be used to provideintegrated home security and automation management. The security panelcan be connected to the security cloud server selectively through one ofmultiple communication interfaces (e.g., selectively using one ofmultiple connection options, such as Ethernet, Wi-Fi, and cellular) sothat the security panel remains connected to the security cloud serverat all times and provides seamless security and automation services.

The security communicator device can at least partially self-program tocommunicate with an existing local security panel when the securitycommunicator device is connected to the existing panel. When aninstaller connects a security communicator device to an existing panelat the premise, the security communicator device can automaticallydetect hardware connections with and signals from the existing localsecurity panel, and adapt itself to permit for communication with theexisting local security panel to take over at least partially thefeatures and functionalities of the existing local security panel. Someembodiments of the home security system can operate to blend informationfrom an existing local security platform (e.g., a legacy system orlegacy system alarms) with other inputs from sensors and devices thatare added to the home security system, and provide for integratedcontrol of security and automation devices at premises where theexisting local security platform is located. Further, the home securitysystem can operate to select from among multiple different communicationchannels to establish communication between a security communicatordevice and a cloud computing system.

Some embodiments of the home security system can operate to blendinformation from an existing local security platform (e.g., a legacysystem or legacy system alarms) with other inputs from sensors anddevices that are added to the home security system, and provide forintegrated control of security and automation devices at premises wherethe existing local security platform is located. Further, the homesecurity system can operate to select from among multiple differentcommunication channels to establish communication between a securitycommunicator device and a cloud computing system.

Some embodiments of the home security system can permit for security andautomation devices (e.g., cameras, sensors, etc.) in the system to beremotely set up and configured through a security integration system,such as the security communicator device and/or the security cloudserver, instead of being set up and configured directly through acommunication network (e.g., a home router). Further, local changes tothe communication network environment at a premises, such as changinginternet providers and credentials, can be provisioned and updated onthe security and automation devices through the security integrationsystem at the premises.

Some embodiments of the home security system can selectively choosemultiple routes for signals (e.g., data streams) from security andautomation devices to different devices such as output devices. Further,some embodiments of the home security system can operate to select fromamong multiple different communication channels to establishcommunication between a security communicator device and a cloudcomputing system.

Some embodiments of the home security system include one or morecomputing devices with an integrated user interface for outputtingsecurity and automation information and receiving a user input ofcontrolling the system. The user interface is configured to integrateoutputs from the existing local security platform and outputs from thesecurity communicator device and associated peripheral devices, andpresent a blend of information for the entire home security system,thereby providing for integrated view and control of security andautomation devices at the premises.

Communicator devices, systems, and methods are described that canupgrade or “takeover” an existing home security system. Such devices,systems, and methods, can function to enhance an existing home securitysystem with one or more home automation, alarm, and/or surveillancefeatures. Various example embodiments include a triple alarm pathcapable of communicating across multiple communication paths (e.g., asingle selected communication path or multiple communication paths inparallel), a unified dashboard for security, surveillance, and homeautomation features, the ability to add legacy systems over local andremote networks, the ability to view video over a home networkconnection, automatic failover of communication paths, encryption withsensors and other devices, the ability to configure local settings overcellular/mobile data network connection, the ability to add both panelmonitored and/or cloud monitored sensors to these legacy systems, theability to self-configure to the legacy (or new) security system (e.g.,can be performed by sensing various hardware connections and signals andmaking responsive configurations to enable system functionality), theability to select communication path priorities through preferencesestablished in the network services platform, the ability to determineoptimal communication path in the device based on factors including costof data path, availability of data path, latency needs related to thesensor data or other sensor triggered criteria, the ability toautomatically switch from cloud platform control to local control basedon detection by one of the plurality of local WANs enabled by theBAT-Connect, and/or combinations thereof.

In some embodiments described herein, a communicator device isconfigured to provide a takeover device that facilitates upgrade oflegacy security platforms. The communicator device may be configured toenhance an existing legacy security platform with one or more features.For example, the communicator device may interface with the legacysecurity platform to bridge intrusion security, video, and homeautomation with various operating systems (e.g., mobile device operatingsystems). The legacy security platform may include one or morecomponents installed and/or in operation at a premises, and thecommunicator device may be installed at a later time from one or morecomponents of the legacy security platform.

In various exemplary embodiments, the communicator device may utilizehigh-speed, encrypted communication protocols (e.g., such ascommercially available from Alula of St. Paul, Minn.), to allow systemcontrol by various smart devices (e.g., mobile cellular phone, tablet,computer, PDA, etc.).

In an exemplary embodiment, the communicator device includes two ormore, three or more, four or more, or yet additional communicationinterfaces. For example, the communicator device may include cellular,Ethernet, and wireless communication interfaces, each of which may beutilized in parallel or independently. The communicator device mayinclude a housing/frame which contains components of the communicatordevice, and the cellular, Ethernet, and/or wireless communicationinterfaces may be located within the housing/frame. A communicatordevice including multiple communication interfaces, including cellular,Ethernet, and wireless communication interfaces, insulates thecommunication device (and users, installers, contractors, etc.) fromcellular carrier sunsets or other communication protocol obsolescence.

The communicator devices described herein may be compatible withmultiple legacy security platforms from various manufacturers. Forexample, some communicator devices described herein provide universal orwide compatibility with existing security platforms. Wide compatibilitycan facilitate installation, reducing the time required for installationof a communicator device. Furthermore, wide compatibility can simplifyoperations by reducing the types of devices that must be stocked andmanaged. In an example embodiment, the communicator device is configuredto automatically link to control panels manufactured by Honeywell,Interlogix, Napco, and others, such as the Honeywell Vista and DSCPowerSeries, Interlogix NX, Interlogix Concord, and Napco Gemini panels.

The communicator device may be connected efficiently and withoutrequiring complex training. For example, joining the communicator deviceto the keypad bus of an existing panel, the communicator device canautomatically detect the type/brand of panel and adapt to itsspecifications, if appropriate. The communicator device may thusinstantly join as a peripheral device, reducing technician setup time.

In various example embodiments, the communicator device communicateswith one or more video components (e.g., security cameras located at apremises). The communicator device facilitates pairing of such homeautomation devices, intrusion and environmental sensors in a single,mobile experience. Real-time and intuitive controls may be enabledthrough mobile applications (e.g., based on Alula iOS, Android, etc.).

Various communicator devices described herein facilitate upgrade ofservices offerings by dealers. For example, the communicator device mayoptionally include a card (e.g., such as a Z-wave wireless communicationcard), a system may be efficiently enhanced with one or more peripheraldevices, such as automated locks, thermostats, lights, garage doorcontrollers, and other devices (e.g., Z-wave certified devices), toexisting or new installations.

In a mobile application associated with the communicator device, userscan quickly monitor and manage system components, and customize personalrecipes to fit their lives. For example, the communicator device mayfacilitate control of all or most security, surveillance, and automationdevices in a premises using a single mobile application. With only asingle mobile application controlling the smart devices in a home orbusiness, response time from the application command to the deviceaction is perceived to be almost instant.

Communicator devices described herein can facilitate integrated smarthome controls. For example, a communicator device may deliver panel-likeuser controls, with intuitive mobile application and touchpad flows(e.g., such as flows similar to a Connect+ device, commerciallyavailable from Alula of St. Paul, Minn.). In various exampleembodiments, a user can learn a single application experience for bothtake-over and new installs. This can streamline business operations andsimplify training and setup. For example, security professionals canlearn and teach one application.

Various communicator devices described herein can serve to modernizeoutdated security panels. The inventors have found that the addition ofconventional cellular or IP communicators to existing panels are oftenrequires continued use of an outdated LED keypad (e.g., conspicuouslylocated on a wall of the premises) as the primary controller. In variousembodiments, the communicator device described herein includes acontemporary and portable interface. In an example embodiment, thecommunicator device includes a touch display, and may include a tableform-factor having a touchpad. The touchpad of the communicator devicecan be used as a new user control inside the home. In some embodiments,the user interface (e.g., appearance of the interface, controls, etc.)have a uniform appearance when viewed on either the application on amobile device or the touchpad of the communicator device. In someembodiments, a legacy keypad may be linked to the communicator deviceand/or other system components without having to join the user's Wi-Finetwork at the premises.

The communicator device may include various communication interfacesthat facilitate broad compatibility, and that can extend the usefulservice life of legacy systems the communicator device is connectedwith. For example, with IP connections on board (e.g., Ethernet andWi-Fi), the communicator device is less hindered by cell sunsets orcommunication protocol obsolescence. Unlike cellular, the internet willnot likely sunset over the expected useful life of the system. Moreover,multiple communication interfaces provide a backup connection that canpromote robust and reliable communication. For example, with a backupconnection always at the ready, the communicator device facilitatesconstant connectivity. The connection is thus less dependent on anetwork with spotty or intermittent coverage, or that may becomeobsolete. Moreover, in some example embodiments, an auto-switchcapability promotes a constant connection to cellular or IPcommunication paths (e.g., to always maintain alarm reporting).

In various example embodiments, the communicator device includes threepaths of WAN connectivity (e.g., from the single communicator devicehousing/frame). The communicator device thus may link to a cloud service(e.g., such as a cloud service provided by Alula of St. Paul, Minn.)using Ethernet, Wi-Fi or CAT-M1 cellular communication paths. In anexample embodiment, the communicator device is compatible with 5Gcommunication. With CAT-M1 IoT-optimized communications to access thecellular network, the communication device is operational with thecommon and current 4G LTE networks, as well as the newest 5G cellulartechnology. Such flexibility in communication may further reduceexposure to cellular communication protocol obsolescence. The Wi-Ficommunication interface may connect directly to a broadband routerand/or create a Wi-Fi access point for a touchpad associated with thecommunicator device.

In various example embodiments, a communicator device described hereinfacilitates adoption of improved communication protocols, enhancedsecurity, surveillance, and automation features, and reduced dependenceon cellular carriers.

In an example embodiment, the communicator device includes “tip andring” support with keyswitch arming. For example, the device may thus beenabled to be connected to any panel that supports CID reporting codesover a phone line, and keyswitch arming support for remote interactivecontrol. Even when operating in tip/ring/keyswitch mode, home automationand video services can be readily added to these accounts (e.g., bydealers).

Referring to FIG. 1A, an example system 100 is shown that can provideintegrated home security and automation services. The system 100 caninclude a security integration system 110 configured for connection withan existing security platform 120 and enhance the security platform 120with additional features which may not be available from the securityplatform 120.

For example, the existing security platform 120 can be a legacy securityplatform which was previously installed and provided at a premise 102before the security integration system 110 is employed, or othersecurity platforms which may be installed before, when, or after thesecurity integration system 110 is deployed and in operation at thepremise 102. The existing security platform 120 may have limitedfunctionalities and is not capable of providing flexibility in modifyingand expanding a home security and automation environment at the premise102. Examples of the existing security platform 120 include HoneywellVista, DSC PowerSeries, Interlogix, Concord, NX, and Simon panels.

In some implementations, the existing security platform 120 includes anexisting security control device 122, a control panel 123, and a centralmonitoring station 124. The existing security control device 122 can beinstalled in the premise 102 and connects to the control panel 123configured to interact with a user to arm and disarm a home securitysystem. The existing security control device 122 can include, or beconnected to, a sound output device 126 (e.g., a siren, speaker, etc.)which can be activated to output an alarm sound when certain securityevents occur which generate an alarm signal. The existing securitycontrol device 122 can be housed in an enclosure and installed at afixed location while the control panel 123 can be mounted at a fixedlocation and/or potable for easy programming and interaction for users.Alternatively, the existing security control device 122 may beconfigured to be portable. The existing security control device 122 canenable communication with an alarm company (e.g., the central monitoringstation 124) that monitors the premise 102. The control panel 123 can beof various types. For example, the control panel 123 can include akeypad (with numeric and other buttons) to arm/disarm and otherwisemaneuver a security system. The control panel 123 can include atouchpad, voice control, and/or wireless remotes (e.g., key fobs) foradditional functionalities.

The existing security control device 122 provides an interface thatcommunicatively connects the control panel 123 and the centralmonitoring station 124. The existing security control device 122 may beinstalled at a suitable location at the premise and connected to anexisting communication network by using an existing network interfacedevice, such as a telephone interface 125 connected to a telephoneservice 127 or other types of interfaces connected to cable and/orInternet services.

The central monitoring station 124 provides services to monitor a homesecurity system, such as burglar, fire, and other residential orcommercial alarm systems. The central monitoring station 124 may alsoprovide watchman and supervisory services. The central monitoringstation 124 can use telephone lines, mobile lines, and/or radio channelsto connect to the existing security control device 122 and callappropriate authorities in the event an alarm signal is received.

The existing security platform 120 may include one or more sensors 128,such as door sensors, window sensors, motion sensors, etc., which areconnected to the existing security control device 122. The sensors 128can detect predetermined events (e.g., open/closed doors and windows,motions detected, etc.), and generate and transmit sensor signalsrepresentative of such events to the existing security control device122 and/or the central monitoring station 124. The sensors 128 can bedirectly controlled through a user interface (e.g., keypad, buttons,etc.) (e.g., the control panel 123) of the existing security controldevice 122.

Referring still to FIG. 1A, the security integration system 110 caninclude a security communicator device 112 and a security cloud server114. In addition, the security integration system 110 can include a usercontroller 116 and a mobile computing device 118.

The security communicator device 112 is configured for connection with alegacy control panel (e.g., the existing security control device 122) toenhance the existing security platform 120 with additional features. Forexample, the existing security platform 120, which had been deployed ata premise for a while (e.g., years), have limited hardware and/orsoftware capabilities to keep track on technology developmentup-to-date, and thus typically lack additional functionalities tosupport user demands. By way of example, a legacy security platform mayinclude a control panel which is not capable of supporting Z-Wavehome-automation, interactive services, IP connectivity, and/or cellularcommunications capabilities, and/or is incompatible with newerperipheral devices (e.g., one or more of the peripheral devices 130). Asdescribed herein, the security communicator device 112 can be configuredto turn a conventional control panel into an integrated home securitywith broadband and cellular communication capabilities, and furthercombine the home security with home automation to provide smart home asa service platform.

Referring to FIGS. 1A and 1B, the security communicator device 112 canbe configured to connect to the existing security control device 122 by,for example, wiring the security communicator device 112 to the existingsecurity control device 122. In some implementations, the securitycommunicator device 112 is configured to connect to one or more types ofwired communication terminals 170 can be used to connect the securitycommunicator device 112 to the existing security control device 122.Further, the security communicator device 112 can provide one or moretypes of connection terminals 172 for connection with the existingsecurity control device 122. For example, a control panel can provide adata bus, telephone lines, and/or other suitable communicationinterfaces, and the security communicator device 112 can be connected tothe control panel via any of the communication terminals 170 that isavailable from the control panel. In some implementations, a cable 174is used to provide wired connection between the security communicatordevice 112 and the existing security control device 122. At least oneend of the cable 174 can be provided with a connector 176 to be pluggedinto the terminals 170 and 172. Alternatively, the security communicatordevice 112 can be wirelessly connected to the existing security controldevice 122.

In some implementations, when the security communicator device 112 isconnected to the existing security control device 122, thefunctionalities of the existing security control device 122 and/or othercomponents in the existing security platform 120 can be disabled,limited and/or modified to ensure the operations of the securitycommunicator device 112, the security cloud server 114, and/or othercomponents in the security integration system 110 so that the entiresecurity and automation components in the premise are fully integratedand centralized by the security integration system 110. In addition oralternatively, the existing security control device 122 can bedisconnected from the existing communication network (e.g., telephone,cable, and/or Internet services).

As described herein, in an example embodiment, the security communicatordevice 112 is configured to be at least partially self-programming whenconnected to the existing security control device 122. For example, thesecurity communicator device 112 can automatically detect a type of theexisting security control device 122, or features and functionality ofthe existing security control device 122, when connected to the existingsecurity control device 122. Automatic detection may facilitateinstallation with the existing security platform 120.

Referring to FIG. 1A, the security communicator device 112 can beconnected to the security cloud server 114 using various communicationprotocols. The security communicator device 112 includes a plurality ofcommunication interfaces 140. For example, the communication interfaces140 include one or more broadband interfaces, such as a wiredcommunication interface 142 (e.g., Ethernet) and a wirelesscommunication interface 144 (e.g., Wi-Fi). In addition, thecommunication interfaces 140 can include a cellular communicationinterface 146 (e.g., 4G/LTE, CAT M1 for 5F transition, etc.). Inaddition or alternatively, the security communicator device 112 caninclude other wired or wireless communication interfaces. Thus, thesecurity communicator device 112 is capable of providing multiple-path(e.g., triple-path) cloud connectivity. The security communicator device112 can communicate security events (e.g., alarm) and/or home automationevents, or other data, via one or more of the communication interfaces140.

The broadband interfaces of the security communicator device 112, suchas the wired communication interface 142 and the wireless communicationinterface 144, can connect to a broadband router 160 which providesaccess to one or more networks 162. Broadband communications between thesecurity communicator device 112 and the security cloud server 114 canbe established via the network(s) 162 and the router 160 to which thesecurity communicator device 112 is connected.

The communication interfaces 140 can be selected based on one or morefactors, such as availability, quality, speed, cost of utilizingcommunication paths, and other requirements. In addition oralternatively, the priorities among the communication interfaces 140 ofthe security communicator device 112 can be determined throughpreferences established in a network services platform. By way ofexample, a cost may be considered to select the lowest-costcommunication path (e.g., the wireless communication interface 144).Alternatively or additionally, a communication interface can be selectedbased on available bandwidth, such as where a particular communicationpath is unavailable, or for a communication having particular bandwidthrequirements. In an example embodiment, the security communicator device112 can automatically select a particular communication path, and/orswitch between communication paths, promoting reliable and robustcommunication with the security cloud server 114 or other remotecomputing devices.

As illustrated in FIG. 1A, the security communicator device 112 can addone or more peripheral devices 130. Such peripheral devices 130 were notpart of the existing security platform 120, and are to be integratedwith the existing security platform 120 after the security communicatordevice 112 is connected to the existing security platform 120. Theperipheral devices 130 being added may be incompatible with the existingsecurity platform 120 if directly connected to the existing securityplatform 120, but can be integrated with the existing security platform120 if connected through the security communicator device 112. Thesecurity communicator device 112 is configured to operate with suchperipheral devices 130 such that the peripheral devices 130 can be usedwith the existing security platform 120 to enhance its functionalities.The peripheral devices 130 can be connected to the security communicatordevice 112 via one or more wired or wireless communication protocols,such as Wi-Fi, Bluetooth, etc., which can facilitate addition of theperipheral devices 130.

In some implementations, the peripheral devices 130 include securitydevices 132 and home automation devices 134. Examples of the securitydevices 132 include door and window sensors, automated locks, alarms,lighting, motion detectors, security cameras, glass break detectors, andother suitable security components. Surveillance cameras and motionsensors work hand in hand with allowing home owners to keep an eye onareas of their home that they might not have access to at the moment.Motion sensors create zones which cannot be accessed without sounding analarm. In addition or alternatively, cameras can be set up to detect anymovement and display it on the owner's account. Glass break detectorsare usually installed near glass doors or a window front of a store.Some examples of glass break detectors can use a microphone to detectwhen a pane of glass is broken or shattered. By monitoring the sound andvibrations the alarm only reacts to sounds above a certain threshold toavoid false alarms.

Examples of the home automation devices 134 include thermostats, lights,garage door controllers, sensors, other suitable devices associated homeappliances and electronic devices. The home automation devices 134 mayinclude a heating, ventilation and air conditioning (HVAC) system whichcan be remotely controlled through the security communicator device 112.Further, the security communicator device 112 can be used as a lightingcontrol system that permits for various lighting device inputs andoutputs to communicate with each other and/or with a user interface.Moreover, the home automation devices 134 may include an occupancy-awarecontrol system that can sense the occupancy of the home using, forexample, smart meters and environmental sensors (e.g., CO2 sensors)which can be integrated into a home security system, and triggerautomatic responses for energy efficiency and home comfort applications.Further, the home automation devices 134 may include leak detectors,smoke detectors, CO detectors, devices for tracking pets and babies'movements and controlling pet access rights, air qualitymonitors/controllers, smart kitchen appliances (e.g., coffee machines,ovens, fridge and multi cooker, etc.).

The cloud security server 114 communicates with the securitycommunicator device 112 via one or more communication networks 166, suchas over one or more IP networks 162 (e.g., Ethernet, Wi-Fi, and/or otherIP networks) and/or cellular networks 164 (e.g., 4G LTE, 5G IoT, and/orother cellular networks). The cloud security server 114 can providevarious services related to the security communicator device 112, suchas real-time and/or near real-time data and control access, multipathnotification alternatives, multiple service enablement, and/or othersuitable services. As described herein, such services can be provided toa user across any of a variety of devices, such as the user controller116 (e.g., a touchpad), the mobile computing device 118 (e.g., asmartphone or tablet), and/or other user devices. The services can beprovided to such devices when they are local and/or remote from thepremises where the security communicator device 112 is located.

In some implementations, the cloud security server 114 can communicateswith a media analysis system 136 configured to process and/or analyzemedia data, such as image/video data, obtained from a peripheral device130 (e.g., a surveillance camera or other image/video capturingdevices). For example, such a peripheral device 130 can capture animage/video, and transmit it to the security communicator 112, whichthen transmits it to the security cloud server 114. If necessary, thesecurity cloud server 114 can send the data to the media analysis system136 for management, processing, and/or analysis. Alternatively or inaddition, the security cloud server 114 and/or the security communicatordevice 112 can manage, process, and/or analyze such media data with orwithout communicating with the media analysis system 136.

The user controller 116 can be a remote device that is connected to thesecurity communicator device 112. The user controller 116 provides auser interface for a user to interact with the home security system 100including, for example, the existing security platform 120 (includingthe existing security control device 122 and/or the central monitoringstation 124), the security communicator device 112, the security cloudserver 114, and other security and automation devices. For example, theuser controller 116 can be configured in the form of a touchpad having atouch screen that displays information about the home security systemand provides virtual control elements (e.g., buttons, switches, etc.) toreceive user inputs. In addition or alternatively, the user controller116 can include a physical user interface, such as physical buttons,switches, etc., to receive user inputs.

The mobile computing device 118 can be a user's mobile device which cancommunicate with the security cloud server 114. The mobile computingdevice 118 provides a user interface for a user to interact with thesecurity cloud server 114. For example, the mobile computing device 118includes a touch screen that displays information about the homesecurity system and provides virtual control elements (e.g., buttons,switches, etc.) to receive user inputs. In addition or alternatively,the mobile computing device 118 can include a physical user interface,such as physical buttons, switches, etc., to receive user inputs. Themobile computing device 118 can be connected to the security cloudserver 114 via cellular networks 164. In addition or alternatively, themobile computing device 118 can be connected to the security cloudserver 114 over one or more IP networks 162 (e.g., Ethernet, Wi-Fi,and/or other IP networks). In addition or alternatively, the mobilecomputing device 118 can communicate with the security communicatordevice 112 directly, or via one or more networks (e.g., thecommunication networks 166). In addition or alternatively, the mobilecomputing device 118 can communicate with the existing security controldevice 122, the central monitoring station 124, and/or other securityand automation devices directly, or via one or more networks (e.g., thecommunication networks 166).

The security communicator device 112 can include a translator 150 tofacilitate communication with proprietary encrypted signals from devices(e.g., the sensors 128 and the peripheral devices 130) of the existingsecurity platform 120.

FIG. 1C is a diagram of an example environment 180 that implements thesystem 100 of FIG. 1A to provide integrated home security and homeservices at a premises 182 (e.g., a house). The premises 182 may have aplurality of zones 190A-D (collectively 190), each of which includessensors and devices as part of the integrated home security andautomation system. In the illustrated example, the zones 190 are definedby a plurality of rooms. Other ways to define multiple zones are alsopossible. Alternatively, the entire premises can be controlled as asingle zone.

In some implementations, each zone 190 may be monitored and controlledindependently, such as in different schedules and/or settings, due atleast part to different user settings and/or different groups of sensorsand devices installed. By way of example, a first zone 190A isconfigured such that a door sensor is enabled between 7 PM to 6 AM everyday and a room temperature is set 70° F., while a second zone 190B isconfigured such that a motion sensor is enabled between 10 PM to 5 AMMonday through Saturday and a room temperature is set 68° F.Alternatively, at least some of the zones 190 may be monitored andcontrolled in the same manner.

The zones 190 can include a mix of sensors and devices from the existingsecurity platform 120 and from the security integration system 110. Forexample, the existing security control device 122 can include a doorsensor 128A in a first zone 190A, a window sensor 128B in a third zone190C, and a window sensor 128C in a fourth zone 190D. In this example,the door sensor 128A can be wired to and controlled through the existingsecurity control device 122. For example, the door sensor 128A can beused to monitor the door opening and closing and transmit a door statussignal (e.g., door open/close events) to the existing security controldevice 122 so that the existing security control device 122 determineswhether to generate an alarm signal. In some implementations, the doorsensor 128A may be armed or disarmed by a user who can controls thecontrol panel 123. The window sensors 128B and 128C in the third andfourth zones 190C and 190D can be wirelessly connected and controlled bythe existing security control device 122. The window sensors 128B and128C are used to monitor the window opening and closing and transmitwindow status signals (e.g., window open/close events) to the existingsecurity control device 122 so that the existing security control device122 determines whether to generate an alarm signal. The control panel123 can be used by a user to arm or disarm the window sensors 128B and128C.

As described herein, the security integration system 110 provides thesecurity communicator device 112 that is connected to the existingsecurity control device 122 to integrate and take over the existingsecurity platform 120. In addition, the premises 182 can be providedwith additional security sensors, automation devices, and othercomponents (e.g., the peripheral devices 130) that are connected to thesecurity communicator device 112. For example, a smoke/air sensor 132Dand a motion sensor 132E are installed in the first zone 190A andwirelessly connected to the security communicator device 112. A motionsensor 132C and kitchen equipment 134C disposed in the second zone 190Bare wirelessly connected to the security communicator device 112. Asmoke/air sensor 132A, a television 134A, and a mobile device 118 whichare disposed in the third zone 190C are wirelessly connected to thesecurity communicator device 112. A motion sensor 132B, an airconditioner 134B, and a user controller 116 (e.g., a touchpad) arrangedin the fourth zone 190D are wirelessly connected to the securitycommunicator device 112. As described herein, the security integrationsystem 110 including the security communicator device 112 and thesecurity cloud server 114 operates to centrally manage and control allthe sensors, devices, and components that are connected to the existingsecurity control device 122 and the security communicator device 112.

FIG. 2 is a flowchart of an example method 200 for providing anintegrated home security and automation service by installing a securitycommunicator device at a premise. The method 200 can begin byidentifying a security panel (e.g., the existing security control device122) that exists at a premise (Block 202). For example, an installer canvisit a premise and identify an existing security panel at the premise.Then, the security communicator device (e.g., the security communicatordevice 112) is connected to the security panel (Block 204). In someimplementations, the security communicator device is connected to a databus and/or telephone lines in the security panel. When connected, thesecurity communicator device can be configured to self-configure itselfto the security panel by, for example, sensing hardware connections withand signals transmitted with the security panel, and making responsiveconfigurations to enable system functionality.

The security communicator device can be connected to a security server(e.g., the security cloud server 114) (Block 206). The security servercan provide various services through the security communicator device.

One or more peripheral devices (e.g., the security devices 132 and thehome automation devices 134) can be connected to the securitycommunicator device (Block 208). In some examples, such peripheraldevices are not compatible with the security panel, and the securitypanel may have no hardware or software capability to support theperipheral devices. The security communicator permits for such otherwiseincompatible peripheral devices to be connected to the security paneland integrated into the existing security platform. Therefore, theexisting security platform can be expanded and enhanced with additionalfeatures of the peripheral devices.

User control devices (e.g., the user controller 116 and the mobiledevice 118) can be connected to the security communicator device (Block210). User control devices provide a user interface to enable a user tointeract with the security communicator device and/or the securityserver communicating the security communicator device. In addition oralternatively, the user control devices can communicate with thesecurity panel and/or a central monitoring station (e.g., the centralmonitoring station 124). The user control devices can be connected toremote computing devices (e.g., the security communicator device, thesecurity server, the security panel, and/or the central monitoringstation) via one or more networks of various protocols (e.g., thecommunication networks 166).

When the security communicator device is connected to, and configured tocommunicate with, the security panel, the security server and/or thesecurity communicator device can perform integrated home security andautomation operations (Block 212). Such operations can use sensorsconnected to the security panel, and/or use the peripheral devicesconnected to the security communicator devices. For example, thesecurity server can receive data from the security communicator devicethat has obtained or generated the data using, or related to, thesecurity panel (including sensors connected thereto) and/or peripheraldevices connected to the security communicator device. The securityserver can process the data, and generate and transmit data forcontrolling and managing the security panel, the sensors connected tothe security panel, the security communicator device, the peripheraldevices connected to the security communicator device, etc. In addition,the security server can transmit data to the user control devices toprovide various home security and automation services to a user.

FIG. 3A is a diagram of an example security communicator device 300configured to provide an integrated home security and automationservice. The security communicator device 300 can be used to at leastpartially implement the security communicator device 112 in FIG. 1A. Thesecurity communicator device 300 can include a processor 302, aplurality of communication modules 304, one or more existing panelconnection interfaces 306, one or more peripheral device connectioninterfaces 308, and an antenna 310.

The plurality of communication modules 304 can include an Ethernet port312, a wireless communication module 314 (e.g., Wi-Fi, Bluetooth, NFC,and/or other suitable wireless protocols), and a cellular communicationmodule 316.

The existing panel connection interfaces 306 can be connected toexisting control panels. Depending on the type of an existing controlpanel to be connected, one of the interfaces 306 can be selected andconnected to the existing control panel. The existing panel connectioninterfaces 306 can a data bus interface 322 (e.g., a RS485 connector), aphone line interface 324, and other data communication interfacescompatible with various types of existing control panels.

The peripheral device connection interfaces 308 can be used to connectperipheral devices (e.g., the peripheral devices 130 including thesecurity sensors 132 and the home automation device 134). The peripheraldevice connection interfaces 308 can include interfaces of various wiredor wireless protocols, such as Ethernet, Wi-Fi, Bluetooth, NFC,cellular, etc. The peripheral device connection interfaces 308 can sharehardware and software modules with the existing panel connectioninterfaces 306. The peripheral device connection interfaces 308 enablesperipheral devices to be enrolled into an existing control panel towhich the security communicator device 300 is connected via one or moreof the existing panel connection interfaces 306. In addition oralternatively, peripheral devices can communicate with a cloud platform(e.g., the security cloud server 114) either directly, or through thesecurity communicator device 300 to which the peripheral devices areconnected via one or more of the peripheral device connection interfaces308, so that the premise is monitored by the cloud platform and/or thesecurity communicator device independent of the security offerings fromthe existing control panel. This can allow users having their existingsecurity systems upgraded to include the security communicator device300 to add sensors or other peripheral devices that can be used withouttriggering alarms on the existing security platform. Accordingly, thesecurity communicator device 300 can support an ability to add bothpanel monitored and/or cloud monitored sensors to these legacy systemsvia the existing panel connection interfaces 306. The securitycommunicator device 300 can optionally include one or more internaloptions to enhance the processor 302, such as an automation hardwarechipset/module that is optimized to communicate with and/or processautomation-based information and/or a translator receiver chipset/modulethat is optimized to receive translator communication.

The security communicator device 300 can further include a translatordevice 330 configured to translate protocol between the securitycommunicator device 300 and an existing security platform to which thesecurity communicator device 300 is connected. The translator 330 can beconfigured to provide universal translation between a variety ofdifferent protocols of different devices.

FIG. 3B is a diagram of an example circuit board 350 of a securitycommunicator device, which can be the security communicator device 300of FIG. 3A. The circuit board 350 includes a microcontroller 352 withone or more wireless communication capabilities embedded. Themicrocontroller 352 can integrate Bluetooth, Bluetooth LE, Wi-Fi, and/orother suitable wireless communication interfaces. The circuit board 350includes an Ethernet terminal 354 which can be used for wired connectionto one or more networks via, for example, a router (e.g., the router 160in FIG. 1A). In addition, the circuit board 350 includes a cellularcommunication module 356 for cellular connection to one or more remotecomputing devices, such as the security cloud server 114. The circuitboard 350 includes a cellular SIM card slot 358 for receiving a SIM cardfor cellular communication. The circuit board 350 can include an antenna360 for wireless communication.

The circuit board 350 includes a plurality of different terminals 370,such as a telephone line terminal 372, a power terminal 374, acommunication terminal 376, one or more data bus terminals (such as adata bus terminal 378 and a device link terminal 380), and an opencollector terminal 382. The telephone line terminal 372 (e.g., ring andtip terminal) provides an interface for connection to telephone lines ofan existing control panel (e.g., the existing security control device122). The telephone line terminals can be configured to be wired to atelephone line from the existing security control panel. The preexistingsecurity control panel can be configured to use the telephone line toreport security alarms to a remote central monitoring system.

The data bus terminal 378 (“RS485”) provides an interface for connectionto a data bus of a type of an existing control panel (e.g., the existingsecurity control device 122). The device link terminal 380 (“PC-Link”)provides an interface for connection to a data bus of another type of anexisting control panel (e.g., the existing security control device 122).The data bus terminals are configured to be wired to a data bus of theexisting security control panel. The preexisting security control panelcan receive and transmit signals over the data bus related to securitysystem. The preexisting security control panel can be communicativelyconnected to and receive information on sensed conditions in or aroundthe premises from existing security sensors positioned at the premises.

The communication terminal 376 provides an interface for communicationwith one or more devices or systems. For example, the communicationterminal (e.g., a communications interface) can be configured to beconnected to one or more devices or systems that are not supporteddirectly by the existing security control panel.

The power terminal 374 provides an interface for connection to anelectronic power source. The open collector terminal 382 may be anoutbound control port. For example, it may be configured to drive a“keyswitch arming” input terminal on an existing control panel.

Referring still to FIG. 3B, the security communicator device can includeone or more local device status indicators, such as a device linkindicator 362A, a panel bus indicator 362B, and a power indicator 362C.The device link indicator 362 can indicate on whether the securitycommunicator device connects to one or more devices or systems. Forexample, the device link indicator 362A can signal when one or moredevices or systems are communicatively connected (wirelessly or in awired configuration) to the security communicator device. The panel busindicator 362B can indicate on whether the security communicator deviceis connected to an existing security control system, device, or panel.For example, the security communicator device is wired to the existingsecurity control panel using one of the data bus terminals or thetelephone line terminal, the panel bus indicator 362B can signal toconfirm such connection. The power indicator 362C is configured toindicate on whether the security communicator device is connected to apower source via, for example, the power terminal.

The security communicator device can include network communicationstatus indicators, such as an Ethernet connection indicator 364A, aWi-Fi connection indicator 364B, and a cellular connection indicator364C. The Ethernet connection indicator 364A can indicate a status ofEthernet connection (e.g., between the security communicator device andthe security cloud server) using, for example, the Ethernet port. TheWi-Fi connection indicator 364B can indicate a status of Wi-Ficonnection (e.g., between the security communicator device and thesecurity cloud server) using, for example, the wireless communicationinterface (e.g., the microcontroller 352). The cellular connectionindicator 364C can indicate a status of cellular connection (e.g.,between the security communicator device and the security cloud server)using, for example, the cellular communication interface (e.g., thecellular communication module 356)

In addition, the security communicator device can include a signalstrength indicator 366 to indicate the signal strength of wirelessand/or wired connections, such as the signal strength of one or more ofEthernet connection, Wi-Fi connection, and the cellular connection.

In addition, the security communicator device can include an updatestatus indicator 368 to indicate an update status of the securitycommunicator device. In some implementations, software and/or firmwareupdate to the security communicator device can be transmitted from thesecurity cloud server and/or other remote computing devices connected tothe security communicator device.

The local device status indicators and/or the network communicationstatus indicators can include lighting devices (e.g., LED signal bulbs)that can turn on/off, change their colors, and/or blink at differentfrequencies. Other types of indicators can be used for the local devicestatus indicators.

FIG. 3C illustrates an example housing 390 for a security communicatordevice. The housing 390 can be used to house the security communicatordevice 300 of FIG. 3A or the circuit board 350 of FIG. 3B. The housing390 includes no or minimal user interface. The housing 390 includes anopening 392 at a side to permit access to the Ethernet terminal 354 andother terminals 370 of the device. The housing 390 can include a baseplate 394 and a cover plate 396, which are removably coupled to eachother using, for example, a snap-lock 398.

FIG. 4 illustrates an example operation of an integrated security system400 for centralizing all home security and automation controls. In someimplementations, the integrated security system 400 can be implementedby the security cloud server 114 through the security communicatordevice 112. Alternatively, the integrated security system 400 can beimplemented by the security communicator device 112 with or withoutcommunicating with the security cloud server 114. Alternatively, atleast part of the integrated security system 400 can be implemented inthe existing security platform 120.

The integrated security system 400 can communicate with an existingsecurity panel 402, a video analysis server 404, one or more homesecurity devices 406, one or more home automation devices 408, a centralstation 410, one or more in-home user control devices 412, and one ormore user devices 414.

The integrated security system 400 can receive data 422 from theexisting security panel 402 (e.g., the existing security control device122). The data 422 can include an alarm status, an armed/disarmedstatus, sensor signals, trouble indication, etc. In someimplementations, the integrated security system 400 can transmit commanddata 423 to the existing security panel 402 to control the existingsecurity panel 402.

The video analysis server 404 operates to receive image data (e.g.,still images or video stream) captured using an image capture sensor(e.g., a camera), and process the data for security purposes. Forexample, an image capture sensor can be one of the security devices 406and/or the home automation devices 408, and operates to capture images(e.g., still images or videos) and transmit data 423 for the images tothe video analysis server 404 either directly or via the existingsecurity panel 402 and/or the integrated security system 400 (e.g., thesecurity communicator device 112 and/or the security cloud server 114).The video analysis server 404 can process the received images andprovide video verification data 424 to the integration security system400. In addition, the video analysis server 404 can perform variousanalytics of the images and transmit the results to the integrationsecurity system 400.

The home security devices 406 and the home automation devices 408 cantransmit to the integrated security system 400 data 426, 428representative of detected sensor signals, status signals, and othersuitable signals associated with the devices 406, 408. The home securitydevices 406 and the home automation devices 408 can be existing (e.g.,legacy) devices connected to the existing security panel 402, and/or newdevices being added to the integrated security system 400 independentlyfrom the existing security panel 402. Examples of the home securitydevices 406 include door and window sensors, automated locks, alarms,lighting, motion detectors, security cameras, glass break detectors, andother suitable security components. Examples of the home automationdevices 408 include thermostats, lights, garage door controllers,sensors, occupancy detectors, home appliances, leak detectors, smokedetectors, CO detectors, and other suitable devices associated smarthome controls.

The home automation devices 408 can communicate with the integratedsecurity system 400 in both ways to permit for the integrated securitysystem 400 to control the home automation devices 408. In addition, thehome security devices 406 can communicate with the integrated securitysystem 400 in both ways to permit for the integrated security system 400to control the home security devices 406.

The integrated security system 400 can communicate with the centralstation 410 for various security purposes. For example, the integratedsecurity system 400 can transmit a signal 430 to the central station 410to report an event so that the central station 410 can take appropriateaction, such as calling appropriate authorities (e.g., police or firestation). In addition, the integrated security system 400 can receivefrom the central station 410 a status signal 431 indicative of thestatus of the action being taken. In some implementations, theintegrated security system 400 is connected to the central station 410through the existing security panel 402. Alternatively, the integratedsecurity system 400 can communicate directly with the central station410.

The integrated security system 400 can communicate with the in-home usercontrol devices 412 (e.g., touchpads) to receive user control inputs 432via the in-home user control devices 412, and transmit variousinformation 434 for displaying home security and automation status onthe in-home user control devices 412. Similarly, the integrated securitysystem 400 can communicate with the user devices 414 (e.g., user'smobile devices) to receive user control inputs 436 via the user devices414, and transmit various information 438 for displaying home securityand automation status on the user devices 414.

The integrated security system 400 operates to receive all the data fromthe existing security panel 402, the video analysis server 404, the homesecurity devices 406, the home automation devices 408, the centralstation 410, the in-home user control devices 412, and the user devices414, and can combine or synthesize the data for providing centralized,integrated, and enhanced home security and automation services.

Referring now to FIGS. 5-7 , an example technique 500 for connecting asecurity integration system 502 to an existing security platform 504 andautomatically configuring the security integration system 502 to becompatible with the existing security platform 504. A securitycommunicator device in the security integration system 502 can at leastpartially self-program to communicate with an existing panel in theexisting security platform 502 when the security communicator device isconnected to the existing panel. For example, when connected to theexisting panel, the security communicator device can automaticallydetect a type (e.g., a protocol) of the existing panel, and adapt itselfto permit for communication with the existing panel to take over atleast partially the features and functionalities of the existing panel.Such automatic detection and configuration may facilitate installationwith the existing security platform without complicating setups andconfigurations.

The security integration system 502 can be used to implement thesecurity integration system 110 and/or the integrated security system400, and/or be part of the security integration system 110 and/or theintegrated security system 400. The security integration system 502includes a security communicator device 512 and a security cloud server514, which are similar to the security communicator device 112 and thesecurity cloud server 114. The security cloud sever 514 iscommunicatively connected with the security communicator device 512 viaone or more networks 566, which is similar to the networks 166(including one or more broadband networks and one or more cellularnetworks). The existing security platform 504 is similar to the existingsecurity platform 120, and includes an existing security control device522, which is similar to the existing security control device of theexisting security platform 120.

Similarly to those described in FIG. 1B, the security communicatordevice 512 is capable of being connected to one or more of differentexisting security control devices 522A, 522B, 522C, 522D, etc.(collectively 522) in a wired configuration using a cable 574.Alternatively, the security communicator device 512 can be wirelesslyconnected to one or more existing security control devices 522. Suchexisting security control devices 522 may be made by differentmanufacturers, and use different protocols, functions, and/oroperational models. In the illustrated example, the securitycommunicator device 512 is connected to an existing security controldevice 522C. As described herein, the security communicator device 512can be wired to the existing security control device 522 through one ormore communication interfaces (e.g., data bus, telephone lines, etc.)that are available from the existing security control device 522.

When the security communicator device 512 is connected to the existingsecurity control device 522, the security communicator device 512 can beautomatically configured (e.g., self-configuration) to be compatiblewith the existing security control device 522. For example, the securitycommunicator device 512, when connected, is self-configured without aninstaller's input, to communicate with the existing security controldevice 522 even if a protocol used by the existing security controldevice 522 is not compatible with a protocol of the securitycommunicator device 512. For example, the security communicator device512 is configured to self-configure itself to the existing securitycontrol device 522 by sensing a hardware connection with, and/or asignal transmitted with, the existing security control device 522, andmaking responsive configurations to enable system functionality.

The security communicator device 512 can include a self-configurationmodule 560, a translator 562, and a peripheral device discover module564. The self-configuration module 560 operates to identify a type ofthe connected existing security control system and configure thesecurity communicator device 512 to be compatible with the connectedexisting security control system. The translator 562 operates to enablecommunication between the security communicator device 512 and theconnected existing security control device 522 that use differentprotocols. The peripheral device discover module 564 is configured toautomatically or with limited user assistance discover, enroll, and/orconfigure the security communicator device 512 to, respond to, andpasses on information from peripheral devices 530 (similar to theperipheral devices 130).

An example self-configuration process can be performed by firstconnecting a security communicator device 512 to an existing securitycontrol device 522 (Step A). For example, an installer locates anexisting security control device 522C at the premises, and brings andconnects the security communicator device 512 to the existing securitycontrol device 522C using, for example, a cable 574. The cable 574 canbe connected to data bus, telephone lines, or other availablecommunication interfaces of the existing security control device 522C.Alternatively, the security communicator device 512 can be wirelesslyconnected to the existing security control device 522C at the premises.In some implementations, a wireless communication with the existingsecurity control device 522C may be encrypted, and thus an encryptionprocess may be required to enable a wireless communication between thesecurity communicator device 512 and the existing security controldevice 522C.

When the connection is made between the security communicator device 512and the existing security control device 522C, a test signal 540 can betransmitted to the existing security control device 522C (Step B). Forexample, the security communicator device 512 can transmit to theexisting security control device 522C the test signal that can begenerated by the security communicator device 512 and/or the securitycloud server 514. The test signal 540 can be a preset signal that isdedicated for a self-configuration process, or a signal that istypically generated by the security communicator device 512 and/or thesecurity cloud server 514 in a normal operation.

The security communicator device 512 detects a signal 542 from theexisting security control device 522C (Step C). The signal 542 can be asignal returned from the existing security control device 522C inresponse to the test signal 540 from the security communicator device512. Alternatively, the security communicator device 512 can receive thesignal 542 without sending the test signal 540 as described in Step Babove.

The security communicator device 512 can analyze the signal 542 andidentify a protocol of the existing security control device 522C basedon the analysis (Step D). The security communicator device 512 cananalyze the signal 542 to find the types of data coming from theexisting security control device 522C. One or more aspects of the signal542 can be identified, examples of which include modulation types,frequency shifts, differential signals, data rates, data pack lengths,error checking, and/or other suitable physical and/or logical aspects ofdata. In addition, different physical ports being used can be detectedand used for the signal analysis.

A variety of methods can be used to determine a protocol of the existingsecurity control device 522 based on the identified aspects of thesignal 542. For example, a pattern matching can be used to identify aprotocol that matches one or more of the identified aspects of thesignal 542. In some implementations, protocol data 568 is provided whichprovides a list of protocols that are used by different types ofmultiple existing security control devices 522, and attributes of eachof the protocols. The protocol data 568 can be used to identify aprotocol of the connected existing security control device 522 bycomparing the identified aspects of the signal 542 with the attributesof different protocols provided by the protocol data.

Although the security communicator device 512 is primarily described asanalyzing the signal and identifying the protocol, it is understood thatthe security cloud server 514 can perform at least part of the analysisand identification and communicate with the security communicator device512.

When the protocol of the existing security control device 522 isidentified, the security communicator device 512 can configure itself tobe compatible with the existing security control device 522 (Step E). Insome implementations, the security communicator device 512 is providedwith a translator 562. Self-configuration of the security communicatordevice 512 can include setup of the translator 562 for the existingsecurity control device 522. The translator 562 may be configured toenable communication between the security communicator device 512 and anexisting security control device 522 to which the security communicatordevice 512 is connected, when the security communicator device 512 andthe connected existing security control device 522 use differentprotocols. As illustrated in FIG. 5 , for example, the existing securitycontrol device 522C connected to the security communicator device 512may communicate with associated sensors and other devices 528 (e.g., thesensors 128) using a first protocol 552C (e.g., Protocol #3), andprocess information provided by the sensors and other devices anddetermine an appropriate system operation, such as issuing an alarmmessage. In the meantime, the security communicator device 512 isconfigured to communicate with the peripheral devices 530 (e.g., theperipheral devices 130) using a second protocol 554 (e.g., Protocol #A).The translator 562 is configured to serve integration and translationfunctions so that the security communicator device 512 communicates withthe existing security control device 522 and/or take over at least partof the features and functionalities of the existing security controldevice 522.

Referring still to FIG. 5 , the translator 562 is configured totranslate protocol between the security communicator device 512 and theexisting security control device 522. The translator 562 is configuredto translate one or more multiple protocols 552 (including 552A-D)(e.g., Protocols #1, #2, #3, #4, etc.) to a protocol 554 (e.g., Protocol#A) that is used by the security communicator device 512, and/ortranslate the protocol 554 to the multiple protocols 552. The translator562 may provide universal translation between a variety of differentprotocols 552 of different existing security control devices 522 and theprotocol 554 of the security communicator device 512. This includestranslating between protocols with mismatched features, such astranslating between a first protocol that includes device types and asecond protocol that does not include device types, and translatingbetween a third protocol that uses a single packet to represent an eventand a fourth protocol that uses multiple packets to represent the sameevent. The self-configuration process of the security communicatordevice 512 includes automatically identifying a protocol of the existingsecurity control device 522 to which the security communicator device512, and configuring the translator 562 to be able to translate betweenthe protocol of the existing security control device 522 and theprotocol of the security communicator device 512.

The translator 562 can translate among multiple different protocols byusing a universal/intermediate protocol into which an incoming packet istranslated and then from which the outgoing packet is translated. Forexample, the translator 562 can translate from a first protocol into theuniversal/intermediate protocol and then from the universal/intermediateprotocol into a second protocol. The universal/intermediate protocol canprovide a variety of advantages, including efficiently providing asystem that can translate between multiple different protocols withoutrequiring specific protocol-to-protocol mappings.

FIGS. 6A and 6B illustrate two different example packet, or data,protocols that may be used by a wireless and/or wired security system,such by the translator devices and systems described throughout thisdocument. Protocol #1 shown in FIG. 6A is described in part in U.S. Pat.No. 5,801,626 to Addy, and Protocol #2 shown in FIG. 6B is described inpart in U.S. Pat. No. 4,855,713 to Brunius. The charts of FIGS. 6A and6B show the order and nature of the bits of data that are sent in a datapacket. Protocol #1 is a 64-bit packet, whereas Protocol #2 is a 59-bitpacket. The example Protocol #1 and Protocol #2 are examples of themultiple protocols that the translator devices and systems describedthroughout this document, such as the translator 562, can translatedbetween.

The data packet protocol in FIG. 6A may be referenced, for illustrationpurposes, as an existing system protocol that a universal translatortranslates into another protocol, such as data packet protocol in FIG.6B, which may be referenced as an expansion system protocol. As such,and referring to FIG. 5 , the existing security control device 522 andits peripheral sensors and devices 528 may use the Protocol #1 of FIG.6A, and the security communicator device 512 may use the Protocol #2 ofthe FIG. 6B. That said, it will be appreciated that Protocol #1 may bethe protocol used by the existing system-sensors, and Protocol #2 is theexpansion protocol used by the new system control device and new sensorsthat may be implemented in the system. In addition, the two protocolsmay simply both be used in a new system being installed.

Referring to FIG. 6A, Protocol #1 is a 64 bit protocol, and starts with16 introductory bits that may be referred to as training bits so thereceiver sees that a message is coming (bits B0 through B15). Theintroductory bits include one pre-start bit (B0), 14 synchronizationbits (B1-B14), and one start bit (B15). The synchronization bits have apredefined pattern and may be used to allow a receiver (for example, asystem control device) to synchronize its detection capabilities withthe timing of the transmission so that the information provided later inthe data packet can be accurately and reliably detected. Thesesynchronization bits may also be used to give the receiver time tosettle its AGC (automatic gain control) and antenna switching activitiesin preparation for the data bits to come. Bits B16-B39 provide a uniqueidentifier code for the particular sensor-transmitter device, or inother words, a device ID code. These numbers may be randomly assigned ata factory (with 1×224 different numbers possible), with the idea beingthat it is extremely unlikely that two sensor-transmitters with the sameidentity code will be distributed by the manufacturer for installationin or near the same wireless security system installation, and hence,every sensor-transmitter in a given system will have a unique identifiercode that distinguishes it from the identifier codes of the othersensor-transmitters in the system and any sensor-transmitters used inany neighboring systems.

In some cases, a manufacturer may not utilize all possibilities ofidentity codes (that is, all of the 1×224 different ID codes) forfielded systems. For example, some ID codes (or ranges of ID codes) maybe reserved for future use, testing, or some other reason. There mayalso be restrictions in certain alarm panels (system control devices) onacceptable or valid ID codes, and as such, an integration device mayneed to be aware of this. For example, if an integration device blindlytranslates an ID code for a sensor-transmitter (for example, a Protocol#1 sensor-transmitter) into another format (for example, Protocol #2),the integration device may translate the ID code (for example, for aProtocol #1 sensor-transmitter) to a rejected ID code on that panel (forexample, a panel that is designed to communicate using Protocol #2), andthus would be rejected by the control panel. Accordingly, in these casesthe integration device may check for these cases and ensure that alltransmitted IDs in Protocol #2 are valid ID codes that will be receivedby a Protocol #2 control panel.

It also deserves mention that while some protocols have device typeindicator bits, Protocol #1 shown in FIG. 6A does not, on its face,utilize a device type indicator. Typical device types may be, forexample, a door-window sensor, a smoke sensor, a key fob device, etc.Device type information may useful to the system control device, so thatthe system control device is able to interpret the sensor stateinformation unique to that device type provided by a particularsensor-transmitter, and react appropriately. Although the identity codeinformation would not appear to utilize a device type indicator, it maybe in some cases that the assignment of identity codes is not entirelyrandom, and that certain sets of identity codes (ranges of ID codes, forexample) may be put only in a certain type of sensor-transmitter. Insuch a case, the 24-bit identity code may contain sensor typeinformation that a system control device would interpret as such (forexample, because the ID code is within a range specifically for theparticular device type).

Protocol #1 includes eight sensor state information bits (B40-B47). Thisgroup of bits provides information about the sensor and sensedconditions made by the sensor. The first four of these bits (B40-B43)are state bits for particular pins that may be in the sensor device andconnected to a sensing point. For example, one pin may be connected to areed switch that is able to detect if a door or window is open orclosed. In other words, if the door is open (and the reed switch isnormally closed when the door is closed), the pin would be high (and thebit would be 1), whereas the pin would be low when the door is closed(and the bit would be 0). Another pin may be tied to a tamper switch,intended to detect a situation wherein someone is trying to destroy oropen up a sensor housing to disable the sensing and transmittingcomponents. Another pin may be tied, for example, to external contactsprovided on the sensor-transmitter housing. For example, a singlesensor-transmitter may have a built-in reed switch monitoring a door,and its external contact may be wired to another reed switch thatmonitors a nearby window, for example. Not all the pins for which stateinformation is provided need be used. Indeed, it is often the case thatone or more of the pins are configured so that they are not used, andare always a 1 (tied high) or always a 0 (tied low), for example.

The next sensor state information bit B44 is a low-battery indicator. Asdescribed previously, the sensor-transmitters may be battery operated,and this information may be provided so as to inform a facilityoperator, for example a homeowner, and/or a monitoring company that abattery of a particular one of the sensor-transmitters needs to bereplaced. A one (1) being transmitted for this bit may indicate, forexample, that the battery is low. The next bit B45 is a supervisory bit,which indicates, for example, that the transmission is one that is aperiodic “checking in,” or supervisory transmission, instead of atransmission that was prompted by a state change. Each of thesensor-transmitters may provide a supervisory transmission periodically,for example, every half hour or so, or other periodic intervals.

The next state information bit B47 is a power-up indicator, whichindicates that the sensor-transmitter has just powered up, for example,a battery has just been put in the sensor-transmitter, and this is thefirst transmission being made by the sensor-transmitter. A power-uptransmission may be used, for example, in the enrollment process inwhich sensors to be used with a security system are enrolled into asystem control device, as will be explained in more detail later. Thelast bit B47 of the sensor state information is a bit that indicatesthat the sensor-transmitter has supervisory transmission capability,given that some-sensor transmitters may be configured so that they donot make frequent supervisory transmissions, which may be desirable tosave battery power. In addition, sensors that are taken off-site aretypically not supervised. This may include key fobs, for example.

The final 16 bits are error checking bits, which may be, for example, acyclical redundancy check (CRC). These bits provide information toensure that all of the preceding bits were received and detectedaccurately as a one or a zero, as the case may be. If there is adiscrepancy, a received packet may be ignored, and the next receivedpacket will be used instead.

In operation, a sensor-transmitter using protocol #1 may make atransmission immediately following the occurrence of a state change, forexample, a door has opened, thus changing the state of a correspondingreed switch, and the state of a pin tied to that reed switch. Thetransmission may be done in two sets of five redundant transmissions ofthe entire data packet of 64 bits. For example, upon a door opening, asensor-transmitter may send a first set of five identical packets of 64bits each in rapid succession, followed by a pause, and then a secondset of five of the same identical packets. Thus, in total, atransmission corresponding to a state change may trigger the sending often identical, redundant packets. This redundancy accounts for the factthat multiple different sensor-transmitters may be in the environmenttransmitting at the same time, and so there may be collisions of thosetransmissions that prevent data from being received and interpretedproperly. In one manner in which this protocol may be utilized inpractice, once a particular data packet configuration is determined, all10 subsequent transmissions will be the same, and will not beinterrupted despite that a change in state may have occurred during thecourse of the 10 packets being transmitted.

A supervisory transmission sequence may consist of only one set of fiveredundant packets sent in rapid succession, in that it may not beimportant that any one supervisory transmission be missed. Although halfthe number of packets as set when there is a change of state, theoperation for supervisory transmissions is similar in that all fivepackets are sent with the same packet information, despite that stateinformation may have changed during the course of transmitting all fiveof these identical packets.

Referring now to FIG. 6B, Protocol #2 is a 59-bit protocol, and startswith 16 introductory bits of data (bits B0 through B15). Theintroductory bits include 15 synchronization bits (B0-B14), and onestart bit (B15). As with Protocol #1, the synchronization bits ofProtocol #2 are provided in a predefined pattern and may allow thereceiver (system control device, for example) to synchronize itsdetection capabilities with the timing of the transmission so that theinformation provided later in the data packet can be accurately andreliably detected, and/or give the receiver time to settle its AGC andantenna switching activities in preparation for the data bits to come.

The next set of bits B16-B35 provide a unique identifier code for theparticular sensor-transmitter device. As with Protocol #1, theseidentifier code numbers may be randomly assigned at a factory (with1×220 different numbers possible for this protocol), with the idea beingagain that it is extremely unlikely that two sensor-transmitters withthe same identity code will be distributed by the manufacturer forinstallation in or near the same wireless security system installation.As such, every sensor-transmitter in a given system will have a uniqueidentifier code that distinguishes it from the identifier codes of theother sensor-transmitters in the system and any sensor-transmitters usedin any neighboring systems.

Bits B36-B39 in Protocol #2 are a four-bit device type indicator.Typical device types may be, for example, a door-window sensor, a smokesensor, a key fob device, etc. Sixteen different device types arepossible with protocol #2, owing to the fact that four bits define thedevice type. Device type information may need to be known by the systemcontrol device 106, so that the system control device 106 is able tointerpret the sensor state information provided by a particularsensor-transmitter. For example, in one device type, an external contactswitch may be associated with certain sensor state information bit (forexample, bits B50-B51), whereas in a different device type, those bitsmay be unused. In another example, the interpretation of a key fob maybe programmed to be completely different than a door-window sensor; forexample, the key fob can arm/disarm the security system while thedoor-window sensor does not typically have this ability.

The next set of three bits (B40-B42) are packet count bits. These bitsincrement on each packet that is transmitted. This allows a receiver todetermine if a packet was missed, or that the receiver is receiving aduplicate transmission of a set of eight packets and thus thetransmission can be ignored.

Protocol #2 includes twelve sensor state information bits (B43-B54),four more than Protocol #1. This group of bits in Protocol #2 providesinformation about the sensor and sensed conditions of the sensor as isthe case with the eight sensor state information bits from Protocol #1,but the nature of the state information is quite different between thetwo protocols. For example, Protocol #1 provides information about therecent past (a latch state) in addition to the currently existing stateof the sensor.

The sensor state information bits of Protocol #2 begin with a lowbattery indicator bit (B43), similar to bit B44 from Protocol #1. Theremaining 11 bits (B44-B54) of the sensor state information for Protocol#2 provides state and latch information for five separate channels F1 toF5. These five channels are similar to the pins in Protocol #1, and maybe tied to one or two reed switches, an external switch, a tamperswitch, etc. The F3 channel may be tied to a tamper switch in all devicetypes. Not all of the channels need to be used with everysensor-transmitter.

A state bit for a channel indicates the current state for a particularchannel. For example, if a reed switch for a door tied to channel F1indicates that the door is currently closed, the state bit for F1 (B44)will have a value that indicates a closed state for the door. A latchbit for a channel reflects a latch having been set associated with thechannel going into a state that may in some cases be an alarm condition,such as the opening of the door. Thus, if a door associated with channelF1 is opened, state bit B44 will have a value that indicates the stateof the door is open, and the latch bit B45 will have a value thatindicates the door has been recently opened (for example, a value ofone). The opening of the door sets the latch regardless of whether theopening of the door is an alarm condition or not. That is because if thesystem control device has been armed, the opening of the door will beconsidered an alarm, but if the system is not armed, the opening of thedoor will not be considered to be an alarm. The door sensor-transmitterdoes not know, however, whether the system is armed or not; hence, thelatch is set whenever the door is opened.

The opening of the door initiates the transmission of multiple 59-bitdata packets in rapid succession, as with Protocol #1. In particular, acounter device of the sensor-transmitter may be set to eight, and isdecremented by one as each packet is sent, and so assuming the openeddoor is not immediately closed again, the opening of the door will causeeight 59-bit packets to be sent in rapid succession. The latch is reset(from 1 to 0, for example) when the packet counter decrements zero.

If, before the packet counter device decrements all the way to zero, theopened door is then closed, the counter in the sensor-transmitter willbe reset to eight again, so that a full complement of eight packets aresent for the newly closed condition of the door. The latch bit willremain set (for example, with a value of one) reflective of the factthat the door was recently opened, because as mentioned, the latch bitdoes not reset (to a zero value, for example) until the transmissioncounter device decrements all the way to zero. If the open door, insteadof being closed again before eight packets are sent, instead is closedonly after all of the eight packets are sent, and the latch bit is resetto zero, then the change of state of the door (that is, the closing ofthe door) still initiates a new set of eight 59-bit packets. In thiscase, however, the latch bit is not set to one, because the closing of adoor is not a condition that is indicative of an alarm condition.

As shown in FIG. 6B, each of the first four channels F1 to F4 has astate bit and a single latch bit. That is because each of these channelsis associated with a normally closed contact. The fifth and finalchannel F5 has a state bit and two complementary latch bits, a positivelatch bit (B52) and a negative latch bit (B52). That is because thischannel F5 is associated with an external contact that may have anormally closed contact or a normally open contact. In that a normallyclosed contact will want its latch set upon the contact being opened (analarm condition), the positive latch and associated latch bit B53 servesthat purpose. In that a normally open contact will want its latch setupon the contact being closed (an alarm condition), the negative latchand negative latch bit B52 serves that purpose.

The next three bits (B55-57) of Protocol #2 are parity bits for errorchecking on the bits sent in the preceding bits of information. Thefinal bit (B58) for Protocol #2 is a stop bit.

FIG. 7 is a flowchart of an example process 700 for automaticallyconfiguring a security communicator device. The security communicatordevice, such as the security communicator device 112, can beself-configured when connected to an existing security panel (e.g., alegacy security panel). This can allow an installer to install asecurity communicator device to a legacy security panel without havingto be specially trained in the identification of the legacy securitypanel and the setup of the security communicator device against thelegacy security panel.

The process 700 can begin by detecting hardware connection to the legacysecurity panel (Block 701). For example, when a security communicatordevice is first wired to the legacy security panel by an installer, thesecurity communicator device can automatically detect connection withthe legacy security panel.

A test signal is transmitted to the legacy security panel that has beeninstalled at the premises (Block 702). For example, when a securitycommunicator device is first wired to the legacy security panel by aninstaller, the security communicator device can automatically transmit atest signal to the legacy security panel to monitor the operation of thelegacy security panel in response to the test signal.

A return signal from the legacy security panel is detected (Block 704).For example, the security communicator device can receive a signalreturned from the legacy security panel in response to the test signal.Alternatively, Block 702 is optional, and the security communicatordevice can simply tap a signal from data bus, telephone lines, or otheravailable data transmission lines from the legacy security panel,without transmitting the test signal to the legacy security panel.

The signal from the legacy security panel is analyzed (Block 706). Forexample, the signal can be analyzed to detect one or more aspects of thesignal. Examples of such signal aspects include modulation types,frequency shifts, differential signals, data rates, data pack lengths,error checking, ports being used, and/or other suitable physical and/orlogical aspects of data in the signal.

A protocol of the legacy security panel is determined (Block 708). Theprotocol that is used for communication between the legacy securitypanel and legacy sensors and devices connected thereto is determined.The protocol of the legacy security panel can be determined based on theidentified signal aspects. A variety of methods can be used to determinethe protocol of the legacy security panel. For example, a patternmatching can be used to identify a protocol that matches one or more ofthe identified signal aspects. In some implementations, protocol datacan be stored and provided by, for example, the security communicatordevice and/or a cloud server connected to the security communicatordevice. The protocol data include a list of protocols which are used bydifferent types of legacy security panels. The protocol data can be usedto identify the protocol of the legacy security panel at the premises bycomparing the identified signal aspects with the attributes of differentprotocols provided by the protocol data.

The security communicator device is automatically configured (Block710). For example, the security communicator device can configure itselfto be compatible with the legacy security panel. In someimplementations, the security communicator device is self-configured bysetting a translator for the legacy security panel (Block 712). Forexample, the determined protocol can be used to set up and configure thetranslator such that the translator permits communication between thesecurity communicator device and the legacy security panel which usedifferent protocols.

Referring now to FIGS. 8-10 , an example technique 800 for blendinginformation from an existing security platform 804 with other inputs,such as inputs from peripheral devices 830 (e.g., sensors, automationdevices, etc.) of a security integration system 802, to provide forintegrated control of security and automation devices at a premise.

The security integration system 802 can be used to implement thesecurity integration system 110 and/or the integrated security system400, and/or be part of the security integration system 110 and/or theintegrated security system 400. The security integration system 802includes a security communicator device 812 and a security cloud server814, which are similar to the security communicator device 112 and thesecurity cloud server 114. The security cloud sever 814 iscommunicatively connected with the security communicator device 812 viaone or more networks 866, which is similar to the networks 166(including one or more broadband networks and one or more cellularnetworks). The existing security platform 804 is similar to the existingsecurity platform 120, and includes an existing security control system822, which is similar to the existing security control device of theexisting security platform 120. The existing security control system 822can connect to one or more existing devices 827, such as sensors (e.g.,the sensors 128), control panels (e.g., keypads) (e.g., the controlpanel 123), and an audio output device (e.g., the sound output device126). The security communicator device 812 can connect to one or moreperipheral devices 830, such as sensors (e.g., the security sensors 132)and automation devices (e.g., the home automation devices 134).

Similarly to those described in FIG. 1B, the security communicatordevice 812 is capable of being connected to one of different existingsecurity control systems 822 in a wired configuration. Alternatively,the security communicator device 812 can be wirelessly connected to theexisting security control system 822. Such existing security controlsystems 822 may be made by different manufacturers, and use differentprotocols, functions, and/or operational models. As described herein,the security communicator device 812 can be wired to the existingsecurity control system 822 through one or more communication interfaces(e.g., data bus, telephone lines, etc.) that are available from theexisting security control system 822.

When the security communicator device 812 is connected to the existingsecurity control system 822, the existing security control system 822can be disconnected from the existing communication network (e.g.,telephone, cable, and/or Internet services) so that the existingsecurity control system 822 does not communicate with a centralmonitoring station 824 (e.g., the central monitoring station 124). Inaddition or alternatively, the functionalities of the existing securitycontrol system 822 can be at least partially disabled, and/or modifiedso that the security communicator device 812 takes over at least part ofthe operation of the existing security control system 822.

When the security communicator device 812 is connected to the existingsecurity control system 822, the security communicator device 812 canlisten to data from the existing security control system 822. Such datacan include information about alarm status, device status (e.g., statusof an existing device 827 connected to the existing security controlsystem 822), etc. The data can be tapped from the communicationinterface (e.g., data bus, telephone lines, etc.) of the existingsecurity control system 822 to which the security communicator device812 is connected.

In addition, the security communicator device 812 can receive inputsfrom other security and automation devices which are separate from theexisting security control system 822 and connected to the securitycommunicator device 812. For example, the security communicator device812 can receive inputs from peripheral devices 830 (e.g., the peripheraldevices 130), such as sensors, cameras, home automation devices, etc.,connected to the security communicator device 812. Such inputs caninclude sensor/device status, trouble indication, battery status, alarmstatus, and other information associated with the peripheral devices 830connected to the security communicator device 812.

The data from the existing security control system 822 can be blendedwith the inputs from the devices connected to the security communicatordevice 812, and such blended data can be used to determine one or moreactions for controlling at least part of the entire security andautomation system (including both the security integration system 802and the existing security platform 804). For example, as illustratedalso in FIG. 1C, a premise may have a plurality of zones 840 (including840A and 840B) (e.g., the zones 190 in FIG. 1C), each of which may becontrolled independently. Each of the zones 840 may include one or moreexisting devices 827 being part of the existing security platform 804,and/or one or more peripheral devices 830 being added as part of thesecurity integration system 802. The blended data can be used todetermine an appropriate action for controlling a mix of the existingdevices 827 and the peripheral devices 830 in each of the zones 840.

In some implementations, the security cloud server 814 can receive andcombine the data from the existing security control system 822 and theinputs from the peripheral devices 830, and determine one or moreappropriate actions for controlling the existing devices 827 and theperipheral devices 830 through the security communicator device 812and/or the existing security control system 822. Alternatively, at leastpart of such process in the security cloud server 814 can be performedlocally by the security communicator device 812.

The control scheme by the security communicator device 812 can vary fordifferent existing security control systems 822. For example, for anexisting security control system having data bus, the securitycommunicator device can intercept the data bus to take over the controlof the existing security control system (e.g., control alarm). For anexisting security control system without data bus or for an existingsecurity control system that haven't been integrated with the securitycommunicator device, the security communicator device can intercept aphone line from the existing security control system to get information(e.g., alarm report). Further, the security communicator device cantransmit the intercepted data (e.g., alarm report) over to the cloudserver for processing and analysis. In addition, the cloud server canobtain other data (which are not available from legacy systems) fromother sources (existing and new sensors, etc.). The cloud server canprocess the intercepted data (e.g., the alarm report) and such otherdata, and use the data for integrated controls and functionalities withmultiple devices/systems together.

Referring still to FIG. 8 , the security communicator device 812 caninclude a translator 862 that enables communication between the securitycommunicator device 812 and the connected existing security controlsystem 822 that use different protocols. Alternatively, the translator862 is not included in the security communicator device 812 and may beprovided separately.

The existing security control system 822 connected to the securitycommunicator device 812 may communicate with associated existing devices827 using a first protocol 852 (e.g., Protocol #1), and processinformation provided by the sensors and determine an appropriate systemoperation, such as issuing an alarm message. In the meantime, thesecurity communicator device 812 is configured to communicate with theperipheral devices 830 using a second protocol 854 (e.g., Protocol #A).The translator 862 is configured to serve integration and translationfunctions so that the security communicator device 812 communicates withthe existing security control system 822 and/or take over at least partof the features and functionalities of the existing security controlsystem 822.

In some implementations, the translator 862 is configured to translateone or more multiple protocols 852 used by different existing securitycontrol systems to a protocol 854 (e.g., Protocol #A) that is used bythe security communicator device 812, and/or translate the protocol 854to the multiple protocols 852. This includes translating betweenprotocols with mismatched features, such as translating between a firstprotocol that includes device types and a second protocol that does notinclude device types, and translating between a third protocol that usesa single packet to represent an event and a fourth protocol that usesmultiple packets to represent the same event. In some implementations,the translator 862 can translate among multiple different protocols byusing a universal/intermediate protocol into which an incoming packet istranslated and then from which the outgoing packet is translated. Forexample, the translator 862 can translate from a first protocol into theuniversal/intermediate protocol and then from the universal/intermediateprotocol into a second protocol. The universal/intermediate protocol canprovide a variety of advantages, including efficiently providing asystem that can translate between multiple different protocols withoutrequiring specific protocol-to-protocol mappings.

With reference still to FIG. 8 , an example process for integratedsecurity and automation control can be performed by obtaining a signal842 from the existing security control system 822 (Step A). The signal842 can represent a signal generated by one or more existing devices 827and received by the existing security control system 822. The signal 842can include information about sensor status, alarm status, and othersuitable information associated with the existing security controlsystem 822 and/or the existing devices 827 connected to the existingsecurity control system 822.

The security communicator device 812 can receive and translate thesignal 842 to a modified signal 844 (Step B). In some implementations,the security communicator device 812 converts the signal 842 to themodified signal 844 when the protocol of the signal 842 is notcompatible with the protocol of the security communicator device 812.For example, the translator 862 can convert the signal 842 of a firstprotocol (e.g., Protocol #1) to the modified signal 844 of a secondprotocol (e.g., Protocol #A). Once converted, the security communicatordevice 812 can transmit the modified signal 844 to the security cloudserver 814 for analysis (Step C). In embodiments where no translation isneeded, the security communicator device 812 can route the signal 842 tothe security cloud server 814 with no or little modification to thesignal 842.

In addition, a peripheral signal 846 to the security cloud server 814can be obtained from one of more peripheral devices 830 connected to thesecurity communicator device 812 (Step D). For example, the securitycommunicator device 812 receives the peripheral signal 846 from theperipheral devices 830 and transmits it to the security cloud server 814for analysis. The peripheral signal 846 can represent inputs from theperipheral devices 830, such as sensor/device status, troubleindication, battery status, alarm status, and other informationassociated with the peripheral devices 830 connected to the securitycommunicator device 812.

The security cloud server 814 can receive the modified signal 844 (orthe signal 842 if there is no translation) and/or the peripheral signal846, and blend the signals to generate combined data (Step E). Then, thesecurity cloud server 814 can determine a security action based on thecombined data (Step F). In some implementations, security control rules870 are provided and used to determine such a security action. Thesecurity control rules 870 can provide a list of actions to be takenbased on different combinations between possible statuses of existingdevices connected to the existing security control system and possiblestatuses of peripheral devices connected to the security communicatordevice.

The security action includes one or more operations to be performed bythe security communicator device 812, the existing security controlsystem 822, and/or the security cloud server 814, and/or othercomponents associated with the device 812, the system 822, and/or theserver 814.

By way of example, if a sensor signal representative of a motion in aroom (e.g., a zone) is first detected from one of the peripheral devicesconnected to the security communicator device 812, no surveillance imagefor a space outside a house near the room is captured from one of theperipheral devices connected to the security communicator device 812,and an alarm signal representative of an open window is detected fromthe existing security control system 822, then the combination of thedetected sensor signal, no surveillance image, and the alarm signal canlead to a security action that causes the security communicator device812 (and then the existing security control system 822) to stop thealarm, understanding that a resident inside the house accidentally opensthe window without disarming the security system.

The security cloud server 814 can transmit one or more control signals848 to the security communicator device 812 (Step G). The controlsignals 848 can be generated to represent the security action determinedby the security cloud server 814. The security communicator device 812can perform a desired action based on the control signals 848 (Step H).By way of example, the security communicator device 812 can control theperipheral devices 830 according to the control signals 848.

In addition or alternatively, the control signals 848 can include datafor controlling the existing security control system 822 and/or theexisting devices 827 associated with the system 822. In such cases, thesecurity communicator device 812 converts at least part of the controlsignals 848 to one or more modified control signals 850 (Step I). Insome implementations, the security communicator device 812 converts thecontrol signals 848 to the modified control signal 850 when the protocolof the control signals 848 is not compatible with the protocol of theexisting security control system 822. For example, the translator 862can convert the control signals 848 of the second protocol (e.g.,Protocol #A) to the modified control signals 850 of the first protocol(e.g., Protocol #1). Once converted, the security communicator device812 can transmit the modified control signals 850 to the existingsecurity control system 822 (Step J). When receiving the modifiedcontrol signals 850, the existing security control system 822 canperform a desired action based on the modified control signals 850 (StepK). By way of example, the existing security control system 822 cancontrol the existing devices 827 according to the modified controlsignals 850. In embodiments where no translation is needed, the securitycommunicator device 812 can route at least part of the control signals848 to the existing security control system 822 with no or littlemodification to the control signals 848.

FIGS. 9A and 9B is a flowchart of an example method 900 for providingintegrated home security and automation control based on a blend ofinputs from a legacy security panel 902 (e.g., the existing securitycontrol system) and a security communicator 904 (e.g., the securitycommunicator device). As described herein, the security communicator 904and a security cloud 906 are used to upgrade or take over a legacysecurity platform associated with the legacy security panel 902 withadditional functionalities provided by the security communicator 904 andthe security cloud 906. In some implementations, at least somefunctionalities of the legacy security panel 902 can be disabled,limited, and/or modified when connected to the security communicator 904so that the entire security system at the premise are fully integratedand centralized by the security communicator 904 and the security cloud906. For example, the legacy security panel 902 is communicativelydisconnected from a central monitoring station 908, and the securitycloud 906 and/or the security communicator 904 can instead communicatewith the central monitoring station 908 for appropriate actions.

The legacy security panel 902 can receive one or more legacy devicesignals from legacy sensors and other devices connected to the legacysecurity panel 902 (Block 912). The legacy device signals can includeinformation about device status, alarm status, and other informationassociated with the legacy sensors and other devices. The legacysecurity panel 902 transmits the legacy device signals to the securitycommunicator 904 connected to the legacy security panel 902 (Block 914).

The security communicator 904 receives the legacy device signals fromthe legacy security panel 902 (Block 916). In some implementations, thesecurity communicator 904 converts the legacy device signals to modifiedlegacy signals when a protocol used by the legacy security panel 902 isnot compatible with a protocol used by the security communicator 904(Block 918). The modified legacy signals have the protocol compatiblewith the security communicator 904. The security communicator 904transmits the modified legacy signals to the security cloud 906 (Block920).

In addition or alternatively, the security communicator 904 receivesperipheral device signals from peripheral devices (e.g., sensors andautomation devices) connected to the security communicator 904 (Block922). The peripheral device signals can include information about devicestatus, alarm status, and other information associated with theperipheral devices connected to the security communicator 904. Thesecurity communicator 904 transmits the peripheral device signals to thesecurity cloud 906 (Block 924).

The security cloud 906 receives the modified legacy signals from thesecurity communicator (Block 930). In addition or alternatively, thesecurity cloud 906 receives the peripheral device signals from thesecurity communicator (Block 932). The security cloud 906 determinessecurity/automation events based on the modified legacy signals and/orthe peripheral device signals (Block 934). For example, the statuses ofthe devices, structures, and elements being associated with and/ormodified by the legacy devices and/or the peripheral devices can beidentified based on the modified legacy signals and/or the peripheraldevice signals. By way of example, the security cloud 906 can interpretthe modified legacy signals and/or the peripheral device signals todetermine whether a window in a basement is opened, whether a motion isdetected in a living room, whether a refrigerator door is closed in akitchen, whether smoke is detected in an upper room, etc.

The security cloud 906 determines one or more actions to be taken basedon the identified security/automation events (Block 936). Such actionscan include turning on/off an alarming sound, controlling homeautomation devices (e.g., thermostats, air conditioners, heaters,boilers, lights, stoves, refrigerators, etc.), controlling sensors andcameras, sending notifications to user computing devices, reporting toappropriate authorities (e.g., police, fire station, etc.), etc. Thesecurity cloud 906 generates control signals based on the determinedactions and transmit the control signals to the security communicator904 (Block 938).

The security communicator 904 receives the control signals from thesecurity cloud (Block 940). In some implementations, the securitycommunicator 904 converts the control signals to modified controlsignals when the protocol used by the security communicator 904 is notcompatible with the protocol used by the legacy security panel 902(Block 942). The modified control signals have the protocol compatiblewith the legacy security panel 902. The security communicator 904transmits the modified control signals to the legacy security panel 902(Block 944).

The legacy security panel 902 receives the modified control signals fromthe security communicator 904 (Block 946). The legacy security panel 902performs one or more actions based on the modified control signals(Block 948). For example, the legacy security panel 902 processes themodified control signals to identify actions to be taken, and controlthe legacy devices connected to the legacy security panel 902 accordingthe identified actions.

In addition or alternatively, the security communicator 904 performsdesired actions with the peripheral devices based on the control signals(Block 950). For example, the security communicator 904 processes thecontrol signals to identify actions to be taken, and control theperipheral devices connected thereto according to the identifiedactions.

In addition or alternatively, the security cloud 906 performs desiredactions with the central monitoring station 908 based on the determinedactions (Block 952). For example, the desired action may includereporting to the central monitoring station 908 so that the centralmonitoring station 908 takes appropriate actions, such as deployingsecurity personnel, calling authorities, etc. The central monitoringstation receives a request/report from the security cloud 906 andperforms such appropriate actions (Block 954).

Although it is primarily described that the security communicatorreceives and transmits the legacy device signals and the peripheraldevice signals separately, it is understood that the legacy devicesignals and the peripheral device signals are transmitted together, ortransmitted as combined signals, to the security cloud. Further, thesecurity cloud may control both the legacy devices (e.g., existingdevices) and the peripheral devices (e.g., new devices) at the sametime.

Referring to FIG. 10 , example data 1000 are described which provides alist of actions 1010 according to a blend of legacy data 1002 from alegacy security panel and additional data 1004 from a securitycommunicator. The data 1000 can be used to provide the security controlrules 870 in FIG. 8 .

For example, the legacy data 1002 include information associated with alegacy security panel and associated legacy devices, such as sensors,keypads, speakers, etc. For example, the legacy data 1002 can include alegacy device identifier 1012 for identifying each legacy deviceconnected to the legacy security panel, and a status 1014 of each legacydevice.

The additional data 1004 include information associated with a securitycommunicator that is connected to the legacy security panel to integrateand centralize home security and automation control at a premise,thereby updating the legacy security system. In addition oralternatively, the additional data 1004 include information associatedwith peripheral devices which are connected to the securitycommunicator, such as security sensors, automation devices, and othersuitable devices connected to the security communicator. For example,the additional data 1004 can include a peripheral device identifier 1022for identifying each peripheral device connected to the securitycommunicator, and a status 1024 for each peripheral device.

The blended data 1000 provides different permutations of the legacy data1002 and the additional data 1004, and an action to be taken accordingto each permutation. For example, each set 1032 of legacy deviceidentifier 1012 and status 1014 can be combined with each set 1034 ofperipheral device identifier 1022 and status 1024, and each combinationis associated with an action 1036 for controlling the legacy devicesand/or the peripheral devices as a whole.

Referring now to FIGS. 11-13 , an example technique 1100 for remotelysetting up and/or configuring security devices (e.g., sensors, cameras,etc.) through a security integration system 1102 to allow automatedsetup and/or configuration of such devices and permit for the devices tobe immune to changes to local network settings. Such security devicescan include home automation devices.

The security integration system 1102 can be used to implement thesecurity integration system 110 and/or the integrated security system400, and/or be part of the security integration system 110 and/or theintegrated security system 400. The security integration system 1102includes a security communicator device 1112 and a security cloud server1114, which are similar to the security communicator device 112 and thesecurity cloud server 114. The security cloud server 1114 iscommunicatively connected with the security communicator device 1112 viaone or more networks 1166, which are similar to the networks 166(including one or more broadband networks and one or more cellularnetworks). The existing security platform 1104 is similar to theexisting security platform 120, and includes an existing securitycontrol system 1122, which is similar to the existing security controldevice of the existing security platform 120. The existing securitycontrol system 1122 can connect to one or more existing devices 1127,such as sensors (e.g., the sensors 128), control panels (e.g., keypads)(e.g., the control panel 123), and an audio output device (e.g., thesound output device 126). The security communicator device 1112 canconnect to one or more peripheral devices 1130, such as sensors (e.g.,the security sensors 132) and automation devices (e.g., the homeautomation devices 134).

The security integration system 1102 can further include a local networkaccess device 1140 (e.g., the router 160). In some implementations, thelocal network access device 1140 is secured and cannot be accessedwithout using correct local network access information. The localnetwork access device 1140 can be a device that connects to one or morenetworks (e.g., a wireless or wired local area network, a wide areanetwork, etc.). Some examples of the local network access device 1140include Wi-Fi access points and routes, Bluetooth access points androuters, and other suitable access points and routers.

Security devices 1124, such as the existing devices 1127 and theperipheral devices 1130, can detect and transmit measurements, statusinformation, and/or other data, to the security communicator device 1112directly or via other devices such as the existing security controlsystem 1122, the local network access device 1140, or other devicesand/or networks. Such measurements, status information, and/or otherdata can be transmitted from the security communicator device 1112 tothe security cloud server 1114. In addition, the security devices 1124can receive commands or instructions from the security cloud server 1114via the security communicator device 1112 or from the securitycommunicator device 1112.

Similarly to those described in FIG. 1B, the security communicatordevice 1112 is capable of being connected to one of different existingsecurity control systems 1122 in a wired configuration. Alternatively,the security communicator device 1112 can be wirelessly connected to theexisting security control system 1122. Such existing security controlsystems 1122 may be made by different manufacturers, and use differentprotocols, functions, and/or operational models. As described herein,the security communicator device 1112 can be wired to the existingsecurity control system 1122 through one or more communicationinterfaces (e.g., data bus, telephone lines, etc.) that are availablefrom the existing security control system 1122.

When the security communicator device 1112 is connected to the existingsecurity control system 1122, the existing security control system 1122can be disconnected from the existing communication network (e.g.,telephone, cable, and/or Internet services) so that the existingsecurity control system 1122 does not communicate with a centralmonitoring station (e.g., the central monitoring station 124). Inaddition or alternatively, the functionalities of the existing securitycontrol system 1122 can be at least partially disabled, and/or modifiedso that the security communicator device 1112 takes over at least partof the operation of the existing security control system 1122.

Referring to FIG. 11A, security devices 1124 can be remotely provisionedand configured through the security communicator device 1112, instead ofbeing connected to the network 1166 through a local network accessdevice 1140. Such security device 1124 can include the existing devices1127 connected to the existing security control system 1122, and theperipheral device 1130 connected to the security communicator device1112. A security device 1124, such as the existing device 1127 and theperipheral device 1130, can include a roaming engine 1132, aconfiguration engine 1134, and a device identifier 1136.

The roaming engine 1132 operates when the device is in a roaming statewhere the device is not configured and tries to connect to the securitycloud server 1114. In some implementations, in the roaming state, thedevice connects to the security communicator device 1112 directly, orthrough the local network access device 1140 or any open network accessdevice that is available. For example, the roaming engine 1132 operatesto search for an available network access device, such as the securitycommunicator device 1112, which provides connection to the network 1166.When the roaming engine 1132 finds the security communicator device1112, the roaming engine 1132 can attempt to connect to the securitycloud server 1114 through the security communicator device 1112.

The configuration engine 1134 operates when the device has connected tothe security cloud server 1114 through the security communicator device1112. In some implementations, the configuration engine 1134 can receivelocal network access information 1142. For example, the configurationengine 1134 can request and receive local network access information1142 from the security cloud server 1114 through the securitycommunicator device 1112. In addition, the configuration engine 1134 canoperate to store the received local network access information in thememory of the device. The configuration engine 1134 can attempt toconnect to the network 1166 through the local network access device 1140using the local network access information 1142 received from thesecurity cloud server 1114 through the security communicator device1112. The security device can transition from the roaming state to aconfigured state after connecting to the network 1166 through the localnetwork access device 1140.

The device identifier 1136 can be a value that identifies the securitydevice 1124 to the network 1166. For example, the device identifier 1136is a serial number, a media access control (MAC) address, or other typesof data that identifies the security device 1124.

Referring still to FIG. 11A, the security cloud server 1114 stores thelocal network access information 1142. The local network accessinformation 1142 can include parameters the security device 1124 can useto connect to the local network access device 1140. In someimplementations, the local network access information 1140 is stored ina database associated with the security cloud server 1114. In otherimplementations, the local network access information 1142 is storedoutside of the database of the security cloud server 1114, and receivedby the security cloud server 1114. The security cloud server 1114 canstore and/or receive up-to-date local network access information 1142 inthe course of maintaining the security integration system 1102. Forexample, if the local network access information 1142 for the localnetwork access device 1140 changes (e.g., the credentials or settings tothe local network access device 1140 are modified by a user, or by a newinternet service provider), the security cloud server 1114 receives suchrevised local network access information from a user via a user inputdevice (e.g., the user controller 116, the mobile device 118, etc.), orfrom the internet service provider that stores the revised local networkaccess information. In addition or alternatively, the revised localnetwork access information can be received from the securitycommunicator device 1112 being connected to the local network accessdevice 1140. The revised local network access information can betransmitted to the security devices so that the security devices areautomatically updated with the revised local network access information,and, therefore, the connection between the security devices and thelocal network access device are maintained without requiring thesecurity devices to be separately reconfigured against the local networkaccess device with the revised local network access information.

In some implantations, the local network access information 1142 caninclude credentials (e.g., wireless password) for the local networkaccess device 1140. In addition or alternatively, the local networkaccess information 1142 can include a service set identifier (SSID) fora wireless LAN network and an associated passphrase. In otherimplementations, the local network access information 1142 can include aBluetooth device name or address and a personal identification number(PIN) code. In yet other implementations, the local network accessinformation 1142 can include other information or parameters for thelocal network access device 1140.

In addition or alternatively, the security communicator device 1112 canstore the local network access information 1142. In someimplementations, the local network access information 1142 can bereceived from the security cloud server 1114. The local network accessinformation 1142 can be updated in the security communicator device 1112as it is updated in the security cloud server 1114. In otherimplementations, the security communicator device 1112 can receive thelocal network access information 1142 via a user input device, such asthe user controller 116 and the mobile device 118, and store theinformation for provisioning and/or configuring security devicesconnected to the security communicator device 1112.

With reference still to FIG. 11A, an example process for automaticallyprovisioning and/or configuring security devices 1124. The process canbegin with connecting the security communicator device 1112 to asecurity device 1124 (Step A). In some implementations, when thesecurity device 1124 is first connected to the security communicatordevice 1112, the device 1124 can be in a roaming state. The securitydevice 1124, such as the peripheral devices 1130, can be connected tothe security communicator device 1112 through the local network accessdevice 1140, or directly paired with the security communicator device1112. Further, the security device 1124, such as the existing devices1127 can be connected to the security communicator device 1112 throughthe existing security control system 1122.

In some implementations, the security communicator device 1112 canreceive a device identifier from the security device 1124 (Step B). Thedevice identifier includes data for uniquely identifying the securitydevice 1124. The security communicator device 1112 can request networkaccess information for the security device 1124 (Step C). The requestcan be transmitted to the security cloud server 1114 (Step D). In someimplementations, the request can include the device identifier so thatthe security cloud server 1114 can retrieve the network accessinformation for the security device 1124 associated with the deviceidentifier. The security cloud server 1114 can provide the requestednetwork access information to the security communicator device 1112(Step E). The security communicator device 1112 transmits the receivednetwork access information to the security device 1124 (Step F) so thatthe security device 1124 is automatically connected to the local networkaccess device 1140 using the network access information.

Referring to FIG. 11B, another example process of automaticallyprovisioning and/or configuring security devices 1124. The process canbegin with connecting the security communicator device 1112 to the localnetwork access device 1140 (Step G). To connect and configure thesecurity communicator device 1112 to the local network access device1140, local network access information (e.g., credentials for the localnetwork access device 1140) can be provided via a user input device(e.g., the user controller 116, the mobile device 118, or a userinterface in the security communicator device 1112), or from thesecurity cloud server 1114. The local network access information can bestored in the security communicator device 1112 (Step H).

The security communicator device 1112 is connected to a security device1124 (Step I).). In some implementations, when the security device 1124is first connected to the security communicator device 1112, the device1124 can be in a roaming state. The security device 1124, such as theperipheral devices 1130, can be connected to the security communicatordevice 1112 through the local network access device 1140, or directlypaired with the security communicator device 1112. Further, the securitydevice 1124, such as the existing devices 1127 can be connected to thesecurity communicator device 1112 through the existing security controlsystem 1122.

The security communicator device 1112 can retrieve and transmit thelocal network access information 1142 to the security device 1124 (StepJ) so that the security device 1124 is automatically connected to thelocal network access device 1140 using the network access information.

In some implementations, the security communicator device 1112 canrequest the local network access information 1142 from the securitycloud server 1114 (Step K) to obtain any change made to the localnetwork access information 1142. The security cloud server 1114 canprovide the requested network access information to the securitycommunicator device 1112 (Step L), which can be passed to a securitydevice so that the connection of the security device can be maintainedwith the updated network local network access information.

The processes above can be performed when a security device 1124 isinitially connected to the security communicator device 1112 eitherdirectly or through another device, such as the existing securitycontrol system 1122 or the local network access device 1140. In additionor alternatively, the processes can be performed periodically or on apredetermined schedule to update the local network access informationfor the security device 1124. In addition or alternatively, theprocesses can be performed if it is determined that the local networkaccess information is modified for the security device 1124.

Although it is primarily described that the security communicator device1112 is used as an intermediary for remote provisioning and/orconfiguration, other devices, such as the user controller 116 and themobile device 118, can be alternatively or additionally used to performat least part of the process.

FIG. 12 is a flowchart of an example method 1200 for automaticconfiguration of a security device 1202 against a local network accessdevice. The security device 1202 is connected directly or indirectly toa security communicator 1204, and the security communicator 1204 isconnected to a security cloud 1206. The security device 1202 can includea sensor, a camera, and other devices similar to the peripheral device1130 and/or the existing device 1127 described herein.

A connection is established between the security device 1202 and thesecurity communicator 1204 (Blocks 1212). In some implementations, thesecurity device 1202 is connected to the security communicator 1204through a local network access device. For example, the security device1202 is connected to the local network access device in a roaming state,while the security communicator device 1204 is connected and configuredto the local network access device.

In some implementations, the security device 1202 can transmit a deviceID to the security communicator (Block 1214). The device ID includes avalue that uniquely identifies the security device 1202. The securitycommunicator receives the device ID (Block 1216). The securitycommunicator requests local network access information to the securitycloud (Block 1218). The request can include the device ID. The securitycloud 1206 receives the request (Block 1220). The security cloud 1206retrieves and transmits the local network access information (Block1222). The local network access information that is stored in thesecurity cloud 1206 may have been provided by a user who entered thelocal network access information (e.g., using the user controller 116 orthe mobile device 118) when the security communicator was set up. Theuser can also provide updated local network access information when suchinformation is revised. In addition or alternatively, the local networkaccess information may be provided and/or updated by a service provider(e.g., an internet service provider) that provides network servicesthrough the local network access device. In some implementations, thelocal network access information can be specific to the security device1202 connected to the security communicator 604, and can be determinedbased on the device ID of the security device 1202.

The security communicator 1204 receives the local network accessinformation from the security cloud 1206 (Block 1224). The securitycommunicator 1204 transmits the local network access information to thesecurity device 1202 (Block 1226). The security device 1202 receives thelocal network access information (Block 1228). The security device 1202performs provisioning and/or configuration to communicate with the localnetwork access device using the local network access information (Block1230).

In some implementations, the security communicator 1204 can detectdisconnection of the security device 1202 from the local network accessdevice (Block 1232). For example, such disconnection can occur when thelocal network access information for the local network access devicechanges, such as when a user changes the credentials or other settingsfor the local network access device or when the local network accessdevice is replaced with a new device.

The security communicator 1204 can request local network accessinformation to the security cloud 1206 (Block 1234) to obtain new localnetwork access information which has been updated at the security cloud1206. In response, the security cloud 1206 can perform the processes asdescribed in Blocks 1220-1230 so that the security device 1202 remainsconnected to the local network access device using such new localnetwork access information.

FIG. 13 is a flowchart of an example method 1250 for automaticconfiguration of a security device 1202 against a local network accessdevice. The security device 1202 is connected to a security communicator1204, and the security communicator 1204 is connected to a securitycloud 1206. The security device 1202 can include a sensor, a camera, andother devices similar to the security device 130 described herein.

The security cloud 1206 can store local network access information forconnection to a local network access device (Block 1252). In addition,the security cloud 1206 can be updated with new local network accessinformation which replaces the previous local network accessinformation. The local network access information can be provided by auser through a user interface, such as the user controller 116, themobile device 118, and other user input devices, for example when thesecurity communicator is first installed and set up. The user can alsoprovide updated local network access information when such informationis revised by changing the credentials or changing a service provider.In addition or alternatively, the local network access information maybe provided and updated by a service provider (e.g., an internet serviceprovider) that provides network services through the local networkaccess device.

The security communicator 1204 can receive the local network accessinformation (Block 1254) to connect to the local network access device.The local network access information can be transmitted from thesecurity cloud 1206. Alternatively, it can be provided by a user whoinputs the information into the security communicator 604 using an inputdevice (e.g., the user controller 116, the mobile device 118, etc.).

The security communicator 1204 can store the local network accessinformation locally (Block 1256), which can be transmitted to a securitydevice to automatically connect the security device to the local networkaccess device. The local network access information stored in thesecurity communicator 1204 may be updated to reflect any change thereto.Such updated local network access information can be obtained from thesecurity cloud 1206 or by a user via an input device (e.g., the usercontroller 116, the mobile device 118, etc.) to the securitycommunicator 1204. The updated local network access information istransmitted to the security device so that the connection between thesecurity device and the local network access device is maintained evenif the local network access information is modified.

The security communicator 1204 is connected to the security cloud 1206(Blocks 1258 and 1260) via one or more networks (e.g., broadband orcellular connection). When a broadband network is used, the securitycommunicator 1204 can be connected to the security cloud 1206 via thelocal network access device using the local network access information.

A connection is established between the security device 1202 and thesecurity communicator 1204 (Blocks 1262). In some implementations, thesecurity device 1202 is connected to the security communicator 1204through a local network access device. For example, the security device1202 is connected to the local network access device in a roaming state,while the security communicator device 1204 is connected and configuredto the local network access device.

The security communicator 1204 retrieves and transmits the local networkaccess information to the security device 1202 (Block 1264). Thesecurity device 1202 receives the local network access information(Block 1266). The security device 1202 performs provisioning and/orconfiguration to communicate with the local network access device usingthe local network access information (Block 1268).

Referring now to FIGS. 14-16 , example techniques for selectivelyrouting signals (e.g., data streams) among different devices in a homesecurity environment are described. An example home security system 1400permits multiple routes for signals to be selectively chosen amongdifferent devices. For example, the home security system 1400 can selectone of multiple routes for data streams (e.g., a video stream) fromsecurity devices 1424 (e.g., a video stream from a surveillance camera)to output devices 1426 (e.g., a display device) through a remotesecurity cloud server 1414 or through a security communicator device1412 locally. Further, the home security system 1400 can select fromamong multiple different communication channels to establishcommunication between a security communicator device 1412 and a securitycloud server 1414. For example, the security communicator device 1412can selectively use one of different types of data communications withthe security cloud server 1414, such as broadband (Ethernet and Wi-Fi)and cellular.

The security integration system 1402 can be used to implement thesecurity integration system 110 and/or the integrated security system400, and/or be part of the security integration system 110 and/or theintegrated security system 400. The security integration system 1402includes a security communicator device 1412 and a security cloud server1414, which are similar to the security communicator device 112 and thesecurity cloud server 114. The security cloud sever 1414 iscommunicatively connected with the security communicator device 1412 viaone or more networks, which is similar to the networks 166 (includingone or more broadband networks and one or more cellular networks). Theexisting security platform 1404 is similar to the existing securityplatform 120, and includes an existing security control system 1422,which is similar to the existing security control device of the existingsecurity platform 120. The existing security control system 1422 canconnect to one or more existing devices 1427, such as sensors (e.g., thesensors 128), control panels (e.g., keypads) (e.g., the control panel123), and an audio output device (e.g., the sound output device 126).The security communicator device 1412 can connect to one or moreperipheral devices 1430, such as sensors (e.g., the security sensors132) and automation devices (e.g., the home automation devices 134).

The security integration system 1402 can include a local network accessdevice 1440 (e.g., the router 160) to enable communication between thesecurity communicator device 1412 and the security cloud server 1414.The local network access device 1440 can be a device that connects toone or more networks (e.g., a wireless or wired local area network, awide area network, etc.). Some examples of the local network accessdevice 1440 include Wi-Fi access points and routes, Bluetooth accesspoints and routers, and other suitable access points and routers.

Alternatively or in addition, the security integration system 1402 canuse a cellular communication network 1464 (e.g., the cellular networks164) between the security communicator device 1412 and the securitycloud server 1414.

The security integration system 1402 can include a user control device1416 (e.g., the user controller 116) that is connected to the securitycommunicator device 1412. The user control device 1416 can be connectedto the security communicator device 1412 through the local networkaccess device 1440, or directly paired with the security communicatordevice 1412 using one or more wireless and/or wired communicationinterfaces (e.g., Bluetooth, Wi-Fi Direct, Zigbee, NFC, and othersuitable wireless or wired communication protocols). The user controldevice 1416 provides a user interface for receiving a user input and/oroutputting information (e.g., alerts, notifications, images, videos,etc.) to the user. The user control device 1416 can provide a displaydevice for displaying such information. The user control device 1416 canbe of various types, such as a mobile computing device with a displayscreen (e.g., a touchpad). In some implementations, a plurality of usercontrol device 1416 can be used which are connected to the securitycommunicator device 1412.

In the security integration system 1402, a user computing device 1418(e.g., the mobile computing device 118) may be used in addition to, oralternatively to, the user control device 1416. The user computingdevice 1418 can be a computing device which is not originally part ofthe security integration system 1402 but later configured to be usedwith the devices in the security integration system 1402. For example,the user computing device 1418 can be a user's own mobile device (e.g.,a smartphone or tablet) that runs a software application designed towork with the security communicator 1412, the security cloud server1414, the existing security control system 1422, and/or the securitydevices 1424 (e.g., the existing devices 1427 and the peripheral devices1430). For example, the user computing device 1418 can be connected tothe security cloud server 1414 via a cellular network (e.g., thecellular network 1464), or via a local network access device (e.g., thelocal network access device 1440).

The security integration system 1402 can communicate with remotecomputing devices, servers, or systems for additional services. Forexample, the security cloud server 1414 in the security integrationsystem 1402 can communicate with a media analysis server 1436 (e.g., themedia analysis system 136). The media analysis server 1436 operates toprocess media data for various purposes. For example, the media analysisserver 1436 can receive from the security cloud server 1414 data streamrepresentative of a video stream obtained by a surveillance camera (asan example of the security device 1424). Such a video stream may betransmitted from the surveillance camera to the cloud server 1414through the security communicator device 1412, and the cloud server 1414can transmit the video stream to the media analysis server 1436 forprocessing. As described herein, the processed media data can betransmitted to the user control device 1416 and/or the user computingdevice 1418 for display along various pathways. For example, theprocessed media data can be transmitted from the media analysis server1436 to the user control device 1416 through the security cloud server1414 and the security communicator device 1412 using the local networkaccess device 1440 or the cellular network 1464. Further, the processedmedia data can be transmitted from the media analysis server 1436 to theuser computing device 1418 through the security cloud server 1414 usingthe broadband network 1462 (through the local network access device1440) or using the cellular network 1464. Alternatively, the processedmedia data can be transmitted from the media analysis server 1436directly to the user control device 1416 and/or the user computingdevice 1418 via one or more networks (e.g., cellular network).

Similarly to those described in FIG. 1B, the security communicatordevice 1412 is capable of being connected to one of different existingsecurity control systems 1422 in a wired configuration. Alternatively,the security communicator device 1412 can be wirelessly connected to theexisting security control system 1422. Such existing security controlsystems 1422 may be made by different manufacturers, and use differentprotocols, functions, and/or operational models. As described herein,the security communicator device 1412 can be wired to the existingsecurity control system 1422 through one or more communicationinterfaces (e.g., data bus, telephone lines, etc.) that are availablefrom the existing security control system 1422.

When the security communicator device 1412 is connected to the existingsecurity control system 1422, the security communicator device 1412 canlisten to data from the existing security control system 1422. Such datacan include information about alarm status, device status (e.g., statusof an existing device 1427 connected to the existing security controlsystem 1422), etc. The data can be tapped from the communicationinterface (e.g., data bus, telephone lines, etc.) of the existingsecurity control system 1422 to which the security communicator device1412 is connected. In addition, the security communicator device 1412can receive inputs from other security and automation devices which areseparate from the existing security control system 1422 and connected tothe security communicator device 1412. For example, the securitycommunicator device 1412 can receive inputs from peripheral devices 1430(e.g., the peripheral devices 130), such as sensors, cameras, homeautomation devices, etc., connected to the security communicator device1412. Such inputs can include sensor/device status, trouble indication,battery status, alarm status, and other information associated with theperipheral devices 1430 connected to the security communicator device1412. The data from the existing security control system 1422 can beblended with the inputs from the devices connected to the securitycommunicator device 1412, and such blended data can be used to determineone or more actions for controlling at least part of the entire securityand automation system (including both the security integration system1402 and the existing security platform 1404).

In some implementations, the security cloud server 1414 can receive andcombine the data from the existing security control system 1422 and theinputs from the peripheral devices 1430, and determine one or moreappropriate actions for controlling the existing devices 1427 and theperipheral devices 1430 through the security communicator device 1412and/or the existing security control system 1422. Alternatively, atleast part of such process in the security cloud server 1414 can beperformed locally by the security communicator device 1412.

Referring to FIGS. 14A-14D, example processes for routing data alongdifferent pathways in the home security system 1400. In these examples,the security communicator device 1412 uses a broadband network (e.g.,Ethernet or Wi-Fi communication) via the local network access device1440, and communicates with the security cloud server 1414.

FIG. 14A illustrates an example pathway for routing data from a securitydevice to an output device in the integrated home security system. Inthis example, a peripheral device 1430 connected to the securitycommunicator device 1412 transmits a device signal 1450 to the securitycommunicator device 1412 (Step A). As described herein, the peripheraldevice 1430 can be a sensor, camera, or other security and/or automationdevices. The device signal 1450 can be generated at the peripheraldevice 1430 and represent measurements, status information, image (stillimage or video), sound, and/or other data stream which may be detectedby the peripheral device 1430.

The security communicator device 1412 receives the device signal 1450from the peripheral device 1430, and transmits the device signal 1450 tothe security cloud server 1414 through one or more broadband networks1462 (e.g., the networks 162) using the local network access device 1440(Step B). In some implementations, the security communicator device 1412can route the device signal 1450 from the peripheral device 1430 to thesecurity cloud server 1414. In other implementations, the securitycommunicator device 1412 can process the device signal 1450 beforetransmitting it to the security cloud server 1414.

When the security cloud server 1414 receives the device signal 1450 fromthe security communicator device 1412, the security cloud server 1414can process the device signal 1450 for analysis or other purposes (StepC). In one example, the device signal 1450 can be processed to identifymedia data, such as images (still images or video) and/or sounds, whichmay be displayed to a user using a media output device (e.g., the usercontrol device 1416 or the user computing device 1418). In anotherexample, the device signal 1450 can be processed to identify the statusinformation and/or measurements obtained by the peripheral device 1430.

The security cloud server 1414 can transmit a processed signal 1452 overthe broadband networks 1462 (Step D). In this example, the user controldevice 1416 is connected to the local network access device 1440. Thus,the processed signal 1452 can be routed through the local network accessdevice 1440 to the user control device 1416 (Step E). In alternativeembodiments, the security cloud server 1414 can transmit the processedsignal 1452 over the cellular network 1464, for example when thebroadband networks 1462 and/or the local network access device 1440 arenot available or do not provide quality connectivity, as illustrated inFIG. 15A below. The processed signal 1452 can be a signal generated bythe security cloud server 1414 or a signal modified from the devicesignal 1450.

The user control device 1416 can output content using the processedsignal 1452 (Step F). In embodiments where the processed signal 1452represents media data stream (e.g., still images or video), the usercontrol device 1416 can display the media conveyed by the processedsignal 1452. In embodiments where the processed signal 1452 includesinformation about sensor status information, the user control device1416 can display or present the sensor status information.

In some embodiments, when the device signal 1450 is, or includes, amedia signal 1454 that represents a media stream (e.g., still images,video, sound, etc.), the media signal 1454, or the device signal 1450including the media signal 1454, can be transmitted to the mediaanalysis server 1436 (Step G) over, for example, one or more networks.The media analysis server 1436 can process the media signal 1454 foranalysis or other purposes (Step H). The media analysis server 1436 cantransmit a processed media signal 1456 to the security cloud server 1414(Step I). The processed media signal 1456 can be the processed signal1452, or be included in the processed signal 1452, which is routed tothe user control device 1416 as described above.

FIG. 14B illustrates an example pathway for routing data from a securitydevice to an output device in the integrated home security system. Thepathway in this example is similar to the pathway in the example of FIG.14A except that the processed signal 1452 that is transmitted from thesecurity cloud server 1414 is transmitted to the security communicatordevice 1412 and routed to the user control device 1416 (Step E′). In theexample of FIG. 14B, the user control device 1416 is directly connectedto the security communicator device 1412 and receives the processedsignal 1452 from the security communicator device 1412, instead of beingrouted directly from the local network access device 1440 (Step E ofFIG. 14A).

FIG. 14C illustrates an example pathway for routing data from a securitydevice to an output device in the integrated home security system. Inthis example, an existing security device 1427 connected to the existingsecurity control system 1422 transmits a device signal 1470 to theexisting security control system 1422 (Step J). As described herein, theexisting security device 1427 can be a sensor, camera, or other securityand/or automation devices which are installed by connecting to theexisting security control system 1422 at the premises. The device signal1470 can be generated at the existing security device 1427 and representmeasurements, status information, image (still image or video), sound,and/or other data stream which may be detected by the existing securitydevice 1427.

The existing security control system 1422 receives the device signal1470 from the existing security device 1427, and transmits the devicesignal 1470 to the security communicator device 1412 (Step K).

In some implementations, the security communicator device 1412 canconvert the device signal 1470 to a converted device signal 1472 (StepL). For example, the security communicator device 1412 can include atranslator 1466 that enables communication between the securitycommunicator device 1412 and the connected existing security controlsystem 1422 that use different protocols. The translator 1466 canconvert the device signal 1470 to the converted device signal 1472 tosatisfy the protocol used by the security communicator device 1412.

For example, the existing security control system 1422 connected to thesecurity communicator device 1412 may communicate with associatedexisting devices 1427 using a first protocol, and process informationprovided by the sensors and determine an appropriate system operation,such as issuing an alarm message. In the meantime, the securitycommunicator device 1412 is configured to communicate with theperipheral devices 1430 using a second protocol. The translator 1466 isconfigured to serve integration and translation functions so that thesecurity communicator device 1412 communicates with the existingsecurity control system 1422 and/or take over at least part of thefeatures and functionalities of the existing security control system1422.

The security communicator device 1412 transmits the converted devicesignal 1472 to the security cloud server 1414 through one or morebroadband networks 1462 (e.g., the networks 162) using the local networkaccess device 1440 (Step M). In some implementations, the securitycommunicator device 1412 can route the converted device signal 1472 tothe security cloud server 1414. In other implementations, the securitycommunicator device 1412 can process the converted device signal 1472before transmitting it to the security cloud server 1414.

When the security cloud server 1414 receives the converted device signal1472 from the security communicator device 1412, the security cloudserver 1414 can process the converted device signal 1472 for analysis orother purposes (Step N). In one example, the converted device signal1472 can be processed to identify media data, such as images (stillimages or video) and/or sounds, which may be displayed to a user using amedia output device (e.g., the user control device 1416 or the usercomputing device 1418). In another example, the converted device signal1472 can be processed to identify the status information and/ormeasurements obtained by the existing security device 1427.

The security cloud server 1414 can transmit a processed signal 1474 overthe broadband networks 1462 (Step O). In this example, the user controldevice 1416 is connected to the local network access device 1440. Thus,the processed signal 1474 can be routed through the local network accessdevice 1440 to the user control device 1416 (Step P). In alternativeembodiments, the security cloud server 1414 can transmit the processedsignal 1474 over the cellular network 1464, for example when thebroadband networks 1462 and/or the local network access device 1440 arenot available or do not provide quality connectivity, as illustrated inFIG. 15B. The processed signal 1474 can be a signal generated by thesecurity cloud server 1414 or a signal modified from the converteddevice signal 1472.

The user control device 1416 can output content using the processedsignal 1474 (Step Q). In embodiments where the processed signal 1474represents media data stream (e.g., still images or video), the usercontrol device 1416 can display the media conveyed by the processedsignal 1474. In embodiments where the processed signal 1474 includesinformation about sensor status information, the user control device1416 can display or present the sensor status information.

In some embodiments, when the converted device signal 1472 is, orincludes, a media signal 1476 that represents a media stream (e.g.,still images, video, sound, etc.), the media signal 1476, or theconverted device signal 1472 including the media signal 1476, can betransmitted to the media analysis server 1436 (Step R) over, forexample, one or more networks. The media analysis server 1436 canprocess the media signal 1476 for analysis or other purposes (Step S).The media analysis server 1436 can transmit a processed media signal1478 to the security cloud server 1414 (Step T). The processed mediasignal 1478 can be the processed signal 1452, or be included in theprocessed signal 1452, which is routed to the user control device 1416as described above.

FIG. 14D illustrates an example pathway for routing data from a securitydevice to an output device in the integrated home security system. Thepathway in this example is similar to the pathway in the example of FIG.14C except that the processed signal 1474 that is transmitted from thesecurity cloud server 1414 is transmitted to the security communicatordevice 1412 and routed to the user control device 1416 (Step P′). In theexample of FIG. 14D, the user control device 1416 is directly connectedto the security communicator device 1412 and receives the processedsignal 1474 from the security communicator device 1412, instead of beingrouted directly from the local network access device 1440 (Step P ofFIG. 14C).

Referring to FIGS. 15A-15B, example processes for routing data alongdifferent pathways in the home security system 1400. In these examples,the security communicator device 1412 uses a cellular network 1464 tocommunicate with the security cloud server 1414.

FIG. 15A illustrates an example pathway for routing data from a securitydevice to an output device in the integrated home security system. Inthis example, a peripheral device 1430 connected to the securitycommunicator device 1412 transmits a device signal 1510 to the securitycommunicator device 1412 (Step U). As described herein, the peripheraldevice 1430 can be a sensor, camera, or other security and/or automationdevices. The device signal 1510 can be generated at the peripheraldevice 1430 and represent measurements, status information, image (stillimage or video), sound, and/or other data stream which may be detectedby the peripheral device 1430.

The security communicator device 1412 receives the device signal 1510from the peripheral device 1430, and transmits the device signal 1510 tothe security cloud server 1414 through the cellular network 1464 (StepV). In some implementations, the security communicator device 1412 canroute the device signal 1510 from the peripheral device 1430 to thesecurity cloud server 1414. In other implementations, the securitycommunicator device 1412 can process the device signal 1510 beforetransmitting it to the security cloud server 1414.

When the security cloud server 1414 receives the device signal 1510 fromthe security communicator device 1412, the security cloud server 1414can process the device signal 1510 for analysis or other purposes (StepW). In one example, the device signal 1510 can be processed to identifymedia data, such as images (still images or video) and/or sounds, whichmay be displayed to a user using a media output device (e.g., the usercontrol device 1416 or the user computing device 1418). In anotherexample, the device signal 1510 can be processed to identify the statusinformation and/or measurements obtained by the peripheral device 1430.

The security cloud server 1414 can transmit a processed signal 1512 tothe security communicator device 1412 over the cellular network 1464(Step X). In alternative embodiments, the security cloud server 1414 cantransmit the processed signal 1512 through the local network accessdevice 1440, as illustrated in FIGS. 14A and 14B. The processed signal1512 can be a signal generated by the security cloud server 1414 or asignal modified from the device signal 1510.

The security communicator device 1412 transmits the processed signal1512 to the user control device 1416 (Step Y). The user control device1416 can output content using the processed signal 1512 (Step Z). Inembodiments where the processed signal 1512 represents media data stream(e.g., still images or video), the user control device 1416 can displaythe media conveyed by the processed signal 1512. In embodiments wherethe processed signal 1512 includes information about sensor statusinformation, the user control device 1416 can display or present thesensor status information.

In some embodiments, when the device signal 1510 is, or includes, amedia signal 1514 that represents a media stream (e.g., still images,video, sound, etc.), the media signal 1514, or the device signal 1510including the media signal 1514, can be transmitted to the mediaanalysis server 1436 (Step AA) over, for example, one or more networks.The media analysis server 1436 can process the media signal 1514 foranalysis or other purposes (Step AB). The media analysis server 1436 cantransmit a processed media signal 1516 to the security cloud server 1414(Step AC). The processed media signal 1456 can be the processed signal1512, or be included in the processed signal 1512, which is routed tothe user control device 1416 as described above.

In some embodiments, the security communicator device 1412 and/or thesecurity cloud server 1414 can be configured such that, if the devicesignal 1510 and/or the processed signal 1512 are to include a large sizeof file (e.g., a video stream), the signals are not transmitted over thecellular network 1464. For example, if the device signal 1510 or theprocessed device signal 1512 includes data which are larger than apredetermined size, the signal will not be transmitted over the cellularnetwork 1464 and can only be transmitted over a broadband network.

FIG. 15B illustrates an example pathway for routing data from a securitydevice to an output device in the integrated home security system. Inthis example, an existing security device 1427 connected to the existingsecurity control system 1422 transmits a device signal 1520 to theexisting security control system 1422 (Step AD). As described herein,the existing security device 1427 can be a sensor, camera, or othersecurity and/or automation devices which are installed by connecting tothe existing security control system 1422 at the premises. The devicesignal 1520 can be generated at the existing security device 1427 andrepresent measurements, status information, image (still image orvideo), sound, and/or other data stream which may be detected by theexisting security device 1427.

The existing security control system 1422 receives the device signal1520 from the existing security device 1427, and transmits the devicesignal 1520 to the security communicator device 1412 (Step AE).

In some implementations, the security communicator device 1412 canconvert the device signal 1520 to a converted device signal 1522 (StepAF). For example, the security communicator device 1412 can include atranslator 1466 that enables communication between the securitycommunicator device 1412 and the connected existing security controlsystem 1422 that use different protocols. The translator 1466 canconvert the device signal 1520 to the converted device signal 1522 tosatisfy the protocol used by the security communicator device 1412.

For example, the existing security control system 1422 connected to thesecurity communicator device 1412 may communicate with associatedexisting devices 1427 using a first protocol, and process informationprovided by the sensors and determine an appropriate system operation,such as issuing an alarm message. In the meantime, the securitycommunicator device 1412 is configured to communicate with theperipheral devices 1430 using a second protocol. The translator 1466 isconfigured to serve integration and translation functions so that thesecurity communicator device 1412 communicates with the existingsecurity control system 1422 and/or take over at least part of thefeatures and functionalities of the existing security control system1422.

The security communicator device 1412 transmits the converted devicesignal 1522 to the security cloud server 1414 through the cellularnetwork 1464 (Step AG). In some implementations, the securitycommunicator device 1412 can route the converted device signal 1522 tothe security cloud server 1414. In other implementations, the securitycommunicator device 1412 can process the converted device signal 1522before transmitting it to the security cloud server 1414.

When the security cloud server 1414 receives the converted device signal1522 from the security communicator device 1412, the security cloudserver 1414 can process the converted device signal 1522 for analysis orother purposes (Step AH). In one example, the converted device signal1522 can be processed to identify media data, such as images (stillimages or video) and/or sounds, which may be displayed to a user using amedia output device (e.g., the user control device 1416 or the usercomputing device 1418). In another example, the converted device signal1522 can be processed to identify the status information and/ormeasurements obtained by the existing security device 1427.

The security cloud server 1414 can transmit a processed signal 1524 overthe cellular network 1464 (Step AI). In alternative embodiments, thesecurity cloud server 1414 can transmit the processed signal 1524through the local network access device 1440, as illustrated in FIGS.14C and 14D. The processed signal 1524 can be a signal generated by thesecurity cloud server 1414 or a signal modified from the converteddevice signal 1522.

The security communicator device 1412 transmits the processed signal1524 to the user control device 1416 (Step AJ). The user control device1416 can output content using the processed signal 1524 (Step AK). Inembodiments where the processed signal 1512 represents media data stream(e.g., still images or video), the user control device 1416 can displaythe media conveyed by the processed signal 1524. In embodiments wherethe processed signal 1524 includes information about sensor statusinformation, the user control device 1416 can display or present thesensor status information.

In some embodiments, when the converted device signal 1522 is, orincludes, a media signal 1526 that represents a media stream (e.g.,still images, video, sound, etc.), the media signal 1526, or theconverted device signal 1522 including the media signal 1526, can betransmitted to the media analysis server 1436 (Step AL) over, forexample, one or more networks. The media analysis server 1436 canprocess the media signal 1526 for analysis or other purposes (Step AM).The media analysis server 1436 can transmit a processed media signal1528 to the security cloud server 1414 (Step AN). The processed mediasignal 1528 can be the processed signal 1452, or be included in theprocessed signal 1452, which is routed to the user control device 1416as described above.

In some embodiments, the security communicator device 1412 and/or thesecurity cloud server 1414 can be configured such that, if the devicesignal 1520, the converted device signal 1522, and/or the processedsignal 1524 are to include a large size of file (e.g., a video stream),the signals are not transmitted over the cellular network 1464. Forexample, if the device signal 1520, the converted device signal 1522, orthe processed device signal 1512 includes data which are larger than apredetermined size, the signal will not be transmitted over the cellularnetwork 1464 and can only be transmitted over a broadband network.

Referring to FIGS. 16A-16D, example processes for routing data alongdifferent pathways in the home security system 1400. In these examples,data are transmitted locally without communicating with the securitycloud server 1414.

FIG. 16A illustrates an example pathway for routing data from a securitydevice to an output device in the integrated home security system. Inthis example, a peripheral device 1430 connected to the securitycommunicator device 1412 transmits a device signal 1610 to the securitycommunicator device 1412 (Step BA). As described herein, the peripheraldevice 1430 can be a sensor, camera, or other security and/or automationdevices. The device signal 1610 can be generated at the peripheraldevice 1430 and represent measurements, status information, image (stillimage or video), sound, and/or other data stream which may be detectedby the peripheral device 1430.

When the security communicator device 1412 receives the device signal1610 from the peripheral device 1430, the security communicator device1412 can process the device signal 1610 for analysis or other purposes(Step BB). In one example, the device signal 1610 can be processed toidentify media data, such as images (still images or video) and/orsounds, which may be displayed to a user using a media output device(e.g., the user control device 1416 or the user computing device 1418).In another example, the device signal 1610 can be processed to identifythe status information and/or measurements obtained by the peripheraldevice 1430.

The security communicator device 1412 can transmit a processed signal1612 using the local network access device 1440 (Step BC). In thisexample, the user control device 1416 is connected to the local networkaccess device 1440. Thus, the processed signal 1612 can be routedthrough the local network access device 1440 to the user control device1416 (Step BD).

The user control device 1416 can output content using the processedsignal 1612 (Step F). In embodiments where the processed signal 1612represents media data stream (e.g., still images or video), the usercontrol device 1416 can display the media conveyed by the processedsignal 1452. In embodiments where the processed signal 1612 includesinformation about sensor status information, the user control device1416 can display or present the sensor status information.

FIG. 16B illustrates an example pathway for routing data from a securitydevice to an output device in the integrated home security system. Thepathway in this example is similar to the pathway in the example of FIG.16A except that the processed signal 1612 that is transmitted from thesecurity communicator device 1412 is transmitted directly to the usercontrol device 1416 (Step BD′). In the example of FIG. 7B, the usercontrol device 1416 is directly connected to the security communicatordevice 1412 and receives the processed signal 1612 from the securitycommunicator device 1412, instead of being routed through the localnetwork access device 1440 (Steps BC and BD of FIG. 16A).

FIG. 16C illustrates an example pathway for routing data from a securitydevice to an output device in the integrated home security system. Inthis example, an existing security device 1427 connected to the existingsecurity control system 1422 transmits a device signal 1620 to theexisting security control system 1422 (Step BF). As described herein,the existing security device 1427 can be a sensor, camera, or othersecurity and/or automation devices which are installed by connecting tothe existing security control system 1422 at the premises. The devicesignal 1620 can be generated at the existing security device 1427 andrepresent measurements, status information, image (still image orvideo), sound, and/or other data stream which may be detected by theexisting security device 1427.

The existing security control system 1422 receives the device signal1620 from the existing security device 1427, and transmits the devicesignal 1620 to the security communicator device 1412 (Step BG).

In some implementations, the security communicator device 1412 canconvert the device signal 1620 to a converted device signal (Step BH).For example, the security communicator device 1412 can include thetranslator 1466 to convert the device signal 1620 to a converted devicesignal suitable for the protocol used by the security communicatordevice 1412.

The security communicator device 1412 can process the device signal 1620(or the converted device signal thereof) for analysis or other purposes(Step BI). In one example, the device signal 1620 can be processed toidentify media data, such as images (still images or video) and/orsounds, which may be displayed to a user using a media output device(e.g., the user control device 1416 or the user computing device 1418).In another example, the device signal 1620 can be processed to identifythe status information and/or measurements obtained by the peripheraldevice 1430.

The security communicator device 1412 can transmit a processed signal1622 using the local network access device 1440 (Step BJ). In thisexample, the user control device 1416 is connected to the local networkaccess device 1440. Thus, the processed signal 1622 can be routedthrough the local network access device 1440 to the user control device1416 (Step BK).

The user control device 1416 can output content using the processedsignal 1622 (Step BL). In embodiments where the processed signal 1622represents media data stream (e.g., still images or video), the usercontrol device 1416 can display the media conveyed by the processedsignal 1622. In embodiments where the processed signal 1622 includesinformation about sensor status information, the user control device1416 can display or present the sensor status information.

FIG. 16D illustrates an example pathway for routing data from a securitydevice to an output device in the integrated home security system. Thepathway in this example is similar to the pathway in the example of FIG.16C except that the processed signal 1622 that is transmitted from thesecurity communicator device 1412 is transmitted directly to the usercontrol device 1416 (Step BK′). In the example of FIG. 16D, the usercontrol device 1416 is directly connected to the security communicatordevice 1412 and receives the processed signal 1622 from the securitycommunicator device 1412, instead of being routed through the localnetwork access device 1440 (Steps BJ and BK of FIG. 16C).

In FIGS. 14-16 , although the user control device 1416 is primarilydescribed as an output device that receives a processed signal andoutputs content associated with the processed signal, other outputdevices, such as the user computing device 1418 can be instead used inthe same or similar manner.

As illustrated in FIGS. 14 and 15 , the security communicator device1412 can operate to select from among multiple different communicationchannels to establish communication between the security communicatordevice 1412 and the security cloud server 1414. For example, thesecurity communicator device 1412 can selectively use one of differenttypes of data communications with the security cloud server 1414, suchas broadband (Ethernet and Wi-Fi) and cellular. Alternatively, thesecurity communicator device 1412 can select and use two or more of suchdifferent data communication channels, and split data stream into two ormore parts and transmit them along the selected different communicationchannels.

In an exemplary embodiment, the security communicator device 1412includes two or more, three or more, four or more, or yet additionalcommunication interfaces. For example, the security communicator device1412 can include cellular, Ethernet, and wireless communicationinterfaces, each of which may be utilized in parallel or independently.The security communicator device 1412 can include a housing/frame whichcontains components of the communicator device, and the cellular,Ethernet, and/or wireless communication interfaces can be located withinthe housing/frame. The security communicator device 1412 that includesmultiple communication interfaces, including cellular, Ethernet, andwireless communication interfaces, insulates the security communicationdevice (and users, installers, contractors, etc.) from cellular carriersunsets or other communication protocol obsolescence.

Such various communication interfaces of the security communicatordevice 1412 can facilitate broad compatibility and extend the usefulservice life of existing security systems (e.g., legacy securityplatforms) to which the security communicator device 1412 is connected.For example, with IP connections on board (e.g., Ethernet and Wi-Fi),the security communicator device 1412 is less hindered by cell sunsetsor communication protocol obsolescence. The Internet will not likelysunset over the expected useful life of the system. Moreover, multiplecommunication interfaces provide a backup connection that can promoterobust and reliable communication. For example, with a backup connectionalways at the ready, the security communicator device facilitatesconstant connectivity. The connection is thus less dependent on anetwork with spotty or intermittent coverage, or that may becomeobsolete. Moreover, in some example embodiments, an auto-switchcapability promotes a constant connection to cellular or IPcommunication paths (e.g., to always maintain alarm reporting).

In various example embodiments, the security communicator device caninclude three paths of WAN connectivity (e.g., from the singlecommunicator device housing/frame). The security communicator devicethus may link to the security cloud server (e.g., such as a cloudservice provided by Alula of St. Paul, Minn.) using Ethernet, Wi-Fi orCAT-M1 cellular communication paths. In an example embodiment, thesecurity communicator device is compatible with 5G communication. WithCAT-M1 IoT-optimized communications to access the cellular network, thesecurity communication device is operational with the common and current4G LTE networks, as well as the newest 5G cellular technology. Suchflexibility in communication may further reduce exposure to cellularcommunication protocol obsolescence. The Wi-Fi communication interfacemay connect directly to a broadband router and/or create a Wi-Fi accesspoint for a touchpad associated with the communicator device. As such,the security communicator device described herein can facilitateadoption of improved communication protocols, enhanced security,surveillance, and automation features, and reduced dependence oncellular carriers.

The security communicator device can be configured to automaticallyswitch from cloud platform control to local control based on detectionof one or more local network accesses available to the securitycommunicator device.

The security communicator device can select communication pathpriorities through preferences established in a network servicesplatform. For example, the security communicator device is configured toselect, from among a plurality of communication paths, an optimalcommunication path to be used by the security communicator device basedon one or more of a plurality of factors. In some implementations, theplurality of factors include costs associated with using the pluralityof communication paths. In some implementations, the plurality offactors include current availability of the plurality of communicationpaths. In some implementations, the plurality of factors include latencyneeds related to sensor data to be transmitted by the communicatordevice. In some implementations, the plurality of factors include sensortriggered criteria. In addition or alternatively, such multiplecommunication options can be prioritized based on, for example, the typeof data being transmitted. In one example, a video stream can beattempted to be sent over broadband first and, if the broadband is notavailable, then over cellular. In another example, the system isconfigured to permit for a video stream to be sent over broadband only,but not over cellular.

Referring now to FIGS. 17-19 , an example technique 1700 for blendinginformation from an existing security platform 1704 with other inputs,such as inputs from peripheral devices 1730 (e.g., sensors, automationdevices, etc.) of a security integration system 1702, and furtherproviding an integrated user control interface for both of the securityintegration system 1702 and the existing security platform 1704, therebypermitting for integrated view and control of security and automationdevices at a premise.

The security integration system 1702 can be used to implement thesecurity integration system 110 and/or the integrated security system400, and/or be part of the security integration system 110 and/or theintegrated security system 400. The security integration system 1702includes a security communicator device 1712 and a security cloud server1714, which are similar to the security communicator device 112 and thesecurity cloud server 114. The security cloud sever 1714 iscommunicatively connected with the security communicator device 1712 viaone or more networks 1766, which is similar to the networks 166(including one or more broadband networks and one or more cellularnetworks). The existing security platform 1704 is similar to theexisting security platform 120, and includes an existing securitycontrol system 1722, which is similar to the existing security controldevice of the existing security platform 120. The existing securitycontrol system 1722 can connect to one or more existing devices 1727,such as sensors (e.g., the sensors 128), control panels (e.g., keypads)(e.g., the control panel 123), and an audio output device (e.g., thesound output device 126). The security communicator device 1712 canconnect to one or more peripheral devices 1730, such as sensors (e.g.,the security sensors 132) and automation devices (e.g., the homeautomation devices 134).

The security integration system 1702 can include a user control device1716 (e.g., the user controller 116) that is connected to the securitycommunicator device 1712. The user control device 1716 can be connectedto the security communicator device 1712 through a local network accessdevice, or directly paired with the security communicator device 1712using one or more wireless and/or wired communication interfaces (e.g.,Bluetooth, Wi-Fi Direct, Zigbee, NFC, and other suitable wireless orwired communication protocols). In some implementations, the usercontrol device 1716 can be a portable device, such as a touchpad. Inother implementations, the user control device 1716 can be fixed at asuitable location. As described herein, the user control device 1716provides an integrated user interface for receiving a user input and/oroutputting a blend of information (e.g., alerts, notifications, images,videos, etc.) to the user. The user control device 1716 can provide adisplay device for displaying such information. The user control device1716 can be of various types, such as a mobile computing device with adisplay screen (e.g., a touchpad). In some implementations, a pluralityof user control device 1716 can be used which are connected to thesecurity communicator device 1712.

In the security integration system 1702, a user computing device 1718(e.g., the mobile computing device 118) may be used in addition to, oralternatively to, the user control device 1716. The user computingdevice 1718 can be a computing device which is not originally part ofthe security integration system 1702 but later configured to be usedwith the devices in the security integration system 1702. For example,the user computing device 1718 can be a user's own mobile device (e.g.,a smartphone or tablet) that runs a software application designed towork with the security communicator 1712, the security cloud server1714, the existing security control system 1722, and/or the securitydevices 1724 (e.g., the existing devices 1727 and the peripheral devices1730). As described herein, such a software application running on theuser computing device 1718 can provide an integrated user interface forreceiving a user input and/or outputting a blend of information to theuser. For example, the user computing device 1718 can be connected tothe security cloud server 1714 via a cellular network (e.g., thecellular network 1764), or via a local network access device.

Similarly to those described in FIG. 1B, the security communicatordevice 1712 is capable of being connected to one of different existingsecurity control systems 1722 in a wired configuration. Alternatively,the security communicator device 1712 can be wirelessly connected to theexisting security control system 1722. Such existing security controlsystems 1722 may be made by different manufacturers, and use differentprotocols, functions, and/or operational models. As described herein,the security communicator device 1712 can be wired to the existingsecurity control system 1722 through one or more communicationinterfaces (e.g., data bus, telephone lines, etc.) that are availablefrom the existing security control system 1722.

When the security communicator device 1712 is connected to the existingsecurity control system 1722, the existing security control system 1722can be disconnected from the existing communication network (e.g.,telephone, cable, and/or Internet services) so that the existingsecurity control system 1722 does not communicate with a centralmonitoring station (e.g., the central monitoring station 124). Inaddition or alternatively, the functionalities of the existing securitycontrol system 1722 can be at least partially disabled, and/or modifiedso that the security communicator device 1712 takes over at least partof the operation of the existing security control system.

When the security communicator device 1712 is connected to the existingsecurity control system 1722, the security communicator device 1712 canlisten to data from the existing security control system 1722. Such datacan include information about alarm status, device status (e.g., statusof an existing device 1727 connected to the existing security controlsystem 1722), etc. The data can be tapped from the communicationinterface (e.g., data bus, telephone lines, etc.) of the existingsecurity control system 1722 to which the security communicator device1712 is connected.

In addition, the security communicator device 1712 can receive inputsfrom other security and automation devices which are separate from theexisting security control system 1722 and connected to the securitycommunicator device 1712. For example, the security communicator device1712 can receive inputs from peripheral devices 1730 (e.g., theperipheral devices 130), such as sensors, cameras, home automationdevices, etc., connected to the security communicator device 1712. Suchinputs can include sensor/device status, trouble indication, batterystatus, alarm status, and other information associated with theperipheral devices 1730 connected to the security communicator device1712.

The data from the existing security control system 1722 can be blendedwith the inputs from the devices connected to the security communicatordevice 1712, and such blended data can be used to determine one or moreactions for controlling at least part of the entire security andautomation system (including both the security integration system 1702and the existing security platform 1704). For example, as illustratedalso in FIG. 1C, a premise may have a plurality of zones 1740 (including1740A and 1740B) (e.g., the zones 190 in FIG. 1C), each of which may becontrolled independently. Each of the zones 1740 may include one or moreexisting devices 1727 being part of the existing security platform 1704,and/or one or more peripheral devices 1730 being added as part of thesecurity integration system 1702. The blended data can be used todetermine an appropriate action for controlling a mix of the existingdevices 1727 and the peripheral devices 1730 in each of the zones 1740.

In some implementations, the security cloud server 1714 can receive andcombine the data from the existing security control system 1722 and theinputs from the peripheral devices 1730, and determine one or moreappropriate actions for controlling the existing devices 1727 and theperipheral devices 1730 through the security communicator device 1712and/or the existing security control system 1722. Alternatively, atleast part of such process in the security cloud server 1714 can beperformed locally by the security communicator device 1712.

The control scheme by the security communicator device 1712 can vary fordifferent existing security control systems 1722. For example, for anexisting security control system having data bus, the securitycommunicator device can intercept the data bus to take over the controlof the existing security control system (e.g., control alarm). For anexisting security control system without data bus or for an existingsecurity control system that haven't been integrated with the securitycommunicator device, the security communicator device can intercept aphone line from the existing security control system to get information(e.g., alarm report). Further, the security communicator device cantransmit the intercepted data (e.g., alarm report) over to the cloudserver for processing and analysis. In addition, the cloud server canobtain other data (which are not available from legacy systems) fromother sources (existing and new sensors, etc.). The cloud server canprocess the intercepted data (e.g., the alarm report) and such otherdata, and use the data for integrated controls and functionalities withmultiple devices/systems together.

Referring still to FIG. 17 , the security communicator device 1712 caninclude a translator 1762 that enables communication between thesecurity communicator device 1712 and the connected existing securitycontrol system 1722 that use different protocols. Alternatively, thetranslator 1762 is not included in the security communicator device 1712and may be provided separately.

The existing security control system 1722 connected to the securitycommunicator device 1712 may communicate with associated existingdevices 1727 using a first protocol 1752 (e.g., Protocol #1), andprocess information provided by the sensors and determine an appropriatesystem operation, such as issuing an alarm message. In the meantime, thesecurity communicator device 1712 is configured to communicate with theperipheral devices 1730 using a second protocol 1754 (e.g., Protocol#A). The translator 1762 is configured to serve integration andtranslation functions so that the security communicator device 1712communicates with the existing security control system 1722 and/or takeover at least part of the features and functionalities of the existingsecurity control system 1722.

In some implementations, the translator 1762 is configured to translateone or more multiple protocols 1752 used by different existing securitycontrol systems to a protocol 1754 (e.g., Protocol #A) that is used bythe security communicator device 1712, and/or translate the protocol1754 to the multiple protocols 1752. This includes translating betweenprotocols with mismatched features, such as translating between a firstprotocol that includes device types and a second protocol that does notinclude device types, and translating between a third protocol that usesa single packet to represent an event and a fourth protocol that usesmultiple packets to represent the same event. In some implementations,the translator 1762 can translate among multiple different protocols byusing a universal/intermediate protocol into which an incoming packet istranslated and then from which the outgoing packet is translated. Forexample, the translator 1762 can translate from a first protocol intothe universal/intermediate protocol and then from theuniversal/intermediate protocol into a second protocol. Theuniversal/intermediate protocol can provide a variety of advantages,including efficiently providing a system that can translate betweenmultiple different protocols without requiring specificprotocol-to-protocol mappings.

With reference still to FIG. 17 , an example process for integrated viewand control of a home security and automation system can be performed byobtaining a signal 1742 from the existing security control system 1722(Step A). The signal 1742 can represent a signal generated by one ormore existing devices 1727 and received by the existing security controlsystem 1722. The signal 1742 can include information about sensorstatus, alarm status, and other suitable information associated with theexisting security control system 1722 and/or the existing devices 1727connected to the existing security control system 1722.

The security communicator device 1712 can receive and translate thesignal 1742 to a modified signal 1744 (Step B). In some implementations,the security communicator device 1712 converts the signal 1742 to themodified signal 1744 when the protocol of the signal 1742 is notcompatible with the protocol of the security communicator device 1712.For example, the translator 1762 can convert the signal 1742 of a firstprotocol (e.g., Protocol #1) to the modified signal 1744 of a secondprotocol (e.g., Protocol #A). Once converted, the security communicatordevice 1712 can transmit the modified signal 1744 to the security cloudserver 1714 for analysis (Step C). In embodiments where no translationis needed, the security communicator device 1712 can route the signal1742 to the security cloud server 1714 with no or little modification tothe signal 1742.

In addition, a peripheral signal 1746 to the security cloud server 1714can be obtained from one of more peripheral devices 1730 connected tothe security communicator device 1712 (Step D). For example, thesecurity communicator device 1712 receives the peripheral signal 1746from the peripheral devices 1730 and transmits it to the security cloudserver 1714 for analysis. The peripheral signal 1746 can representinputs from the peripheral devices 1730, such as sensor/device status,trouble indication, battery status, alarm status, and other informationassociated with the peripheral devices 1730 connected to the securitycommunicator device 1712.

The security cloud server 1714 can receive the modified signal 1744 (orthe signal 1742 if there is no translation) and/or the peripheral signal1746, and process the signals to generate blended data (Step E). Then,the security cloud server 1714 can determine a security action based onthe blended data (Step F). In some implementations, security controlrules 1770 are provided and used to determine such a security action.The security control rules 1770 can provide a list of actions to betaken based on different combinations between possible statuses ofexisting devices connected to the existing security control system andpossible statuses of peripheral devices connected to the securitycommunicator device.

The security action includes one or more operations to be performed bythe security communicator device 1712, the existing security controlsystem 1722, and/or the security cloud server 1714, and/or othercomponents associated with the device 1712, the system 1722, and/or theserver 1714.

By way of example, if a sensor signal representative of a motion in aroom (e.g., a zone) is first detected from one of the peripheral devicesconnected to the security communicator device 1712, no surveillanceimage for a space outside a house near the room is captured from one ofthe peripheral devices connected to the security communicator device1712, and an alarm signal representative of an open window is detectedfrom the existing security control system 1722, then the combination ofthe detected sensor signal, no surveillance image, and the alarm signalcan lead to a security action that causes the security communicatordevice 1712 (and then the existing security control system 1722) to stopthe alarm, understanding that a resident inside the house accidentallyopens the window without disarming the security system.

The security cloud server 1714 can transmit one or more control signals1748 to the security communicator device 1712 (Step G). The controlsignals 1748 can be generated to represent the security actiondetermined by the security cloud server 1714. The security communicatordevice 1712 can perform a desired action based on the control signals1748 (Step H). By way of example, the security communicator device 1712can control the peripheral devices 1730 according to the control signals1748.

In addition or alternatively, the control signals 1748 can include datafor controlling the existing security control system 1722 and/or theexisting devices 1727 associated with the system 1722. In such cases,the security communicator device 1712 converts at least part of thecontrol signals 1748 to one or more modified control signals 1750 (StepI). In some implementations, the security communicator device 1712converts the control signals 1748 to the modified control signal 1750when the protocol of the control signals 1748 is not compatible with theprotocol of the existing security control system 1722. For example, thetranslator 1762 can convert the control signals 1748 of the secondprotocol (e.g., Protocol #A) to the modified control signals 1750 of thefirst protocol (e.g., Protocol #1). Once converted, the securitycommunicator device 1712 can transmit the modified control signals 1750to the existing security control system 1722 (Step J). When receivingthe modified control signals 1750, the existing security control system1722 can perform a desired action based on the modified control signals1750 (Step K). By way of example, the existing security control system1722 can control the existing devices 1727 according to the modifiedcontrol signals 1750. In embodiments where no translation is needed, thesecurity communicator device 1712 can route at least part of the controlsignals 1748 to the existing security control system 1722 with no orlittle modification to the control signals 1748.

Referring still to FIG. 17 , the security communicator device 1712transmits control interface data 1780 to the user control device 1716(Step L). The control interface data 1780 can be at least part of thecontrol signals 1748 that are routed from the security cloud server1714. In some implementations, the control signals 1748 can be thecontrol interface data 1780 and transmitted to the user control device1716. Alternatively, the control interface data 1780 can be generated atthe security communicator device 1712 based on the control signals 1748.The control interface data 1780 can include at least part of the blendeddata generated at the security cloud server 1714, and can be used ingenerating an integrated user interface on the user control device 1716.

The user control device 1716 generates an integrated control interface1782 (Step M). For example, the user control device 1716 includes adisplay screen 1784 and generates the integrated control interface 1782thereon. The integrated control interface 1782 is configured to outputvarious pieces of security and automation information obtained from theblended data generated at the security cloud server 1714. In addition,the integrated control interface 1782 can receive user inputs ofcontrolling the entire integrated system (including the existingsecurity platform, the security communicator device, the peripheraldevices, and the security cloud server). The integrated controlinterface 1782 can be configured to integrate the outputs obtained fromthe existing security control system 1722 and the outputs from thesecurity communicator device 1712 and the peripheral devices connectedto the security communicator device 1712. For example, the integratedcontrol interface 1782 can provide an all-in-one dashboard that displaysboth of the security information from the existing security controlsystem 1722 and the information about the peripheral devices 1730 fromthe security communicator device 1712.

In some implementations, the integrated control interface 1782 canprovide panel-like user controls that integrate accesses to thetake-over devices (connected to the existing security control system1722) and new devices (connected to the security communicator device1712), thereby streamlining installations and operations and simplifyingtraining and setup. Further, the integrated control interface 1782 canpermit for a user to quickly customize security and automation controlsfor the premises.

The user control device 1716 can receive a user input for managingand/or controlling the entire integrated system (Step N). For example, auser can provide a user input by interacting with the integrated controlinterface 1782 displayed on the display screen 1784 of the user controldevice 1716. The user control device 1716 can transmit data about theuser input 1786 to the security communicator device 1712 (Step O). Thesecurity communicator device 1712 can transmit the data to the securitycloud server 1714 for analysis, and/or locally process the data, todetermine and take an appropriate action in response to the user input.

Similarly to the user control device 1716, the user computing device1718 can be used to provide an integrated control interface. In someimplementations, however, the user computing device 1718 can communicatewith the security cloud server 1714 without the security communicatordevice 1712. In other implementations, the user computing device 1718can communicate with the security cloud server 1714 through the securitycommunicator device 1712.

Control interface data 1790 can be transmitted to the user computingdevice 1718 (Step P). The control interface data 1790 can be at leastpart of the control signals 1748 that are transmitted from the securitycloud server 1714. In some implementations, the control signals 1748 canbe the control interface data 1790 and can be transmitted to the usercomputing device 1718. The control interface data 1790 can be identicalor similar to the control interface data 1780. The control interfacedata 1790 can include at least part of the blended data generated at thesecurity cloud server 1714, and can be used in generating an integrateduser interface on the user computing device 1718.

The user computing device 1718 generates an integrated control interface1792 (Step Q). For example, the user computing device 1718 includes adisplay screen 1794 and generates the integrated control interface 1792thereon. Similarly to the integrated control interface 1782, theintegrated control interface 1792 is configured to output various piecesof security and automation information obtained from the blended datagenerated at the security cloud server 1714. In addition, the integratedcontrol interface 1792 can receive user inputs of controlling the entireintegrated system (including the existing security platform, thesecurity communicator device, the peripheral devices, and the securitycloud server). The integrated control interface 1792 can be configuredto integrate the outputs obtained from the existing security controlsystem 1722 and the outputs from the security communicator device 1712and the peripheral devices connected to the security communicator device1712. For example, the integrated control interface 1792 can provide anall-in-one dashboard that displays both of the security information fromthe existing security control system 1722 and the information about theperipheral devices 1730 from the security communicator device 1712.

In some implementations, the integrated control interface 1792 canprovide panel-like user controls that integrate accesses to thetake-over devices (connected to the existing security control system1722) and new devices (connected to the security communicator device1712), thereby streamlining installations and operations and simplifyingtraining and setup. Further, the integrated control interface 1792 canpermit for a user to quickly customize security and automation controlsfor the premises.

In some implementations, the integrated control interface 1792 providedon the user computing device 1718 can be designed to provide identicalor similar appearance as the integrated control interface 1782 on theuser control device 1716, such that users can easily recognize securitystatuses and control the entire integrated system through the same orsimilar-looking user interface on different control devices.

The user computing device 1718 can receive a user input for managingand/or controlling the entire integrated system (Step R). For example, auser can provide a user input by interacting with the integrated controlinterface 1792 displayed on the display screen 1794 of the usercomputing device 1718. The user computing device 1718 can transmit dataabout the user input 1796 to the security cloud server 1714 (Step S).The security cloud server 1714 can process the data to determine andtake an appropriate action in response to the user input.

FIGS. 18A and 18B illustrate example integrated control interfaces onoutput devices. Referring to FIG. 18A, an example integrated controlinterface 1800 is provided on an output device 1802, such as the usercontrol device 1716 and the user computing device 1718. The integratedcontrol interface 1800 can implement the integrated control interface1782 or the integrated control interface 1792.

The integrated control interface 1800 can include a legacy securitysystem section 1810 and a new security system section 1812. The legacysecurity system section 1810 provides information about a legacysecurity system (e.g., the existing security platform 1704). Forexample, the legacy security system section 1810 can show a list oflegacy security devices 1820 (e.g., the existing devices 1727), such assecurity alarms, control panels, speakers, etc. In addition, the legacysecurity system section 1810 can show statuses 1822 of the legacysecurity devices. The legacy security system section 1810 can beconfigured to receive user inputs for each of the legacy securitydevices through, for example, menu controls 1824.

The new security system section 1812 provides information about a newsecurity system (e.g., the security integration system 1702). Forexample, the new security system section 1812 can shows a list of newsecurity and automation devices 1830 (e.g., the peripheral devices1730), such as sensors (e.g., the security sensors 132) and automationdevices (e.g., the home automation devices 134). In addition, the newsecurity system section 1812 can show statuses 1832 of the new securitydevices. The new security system section 1812 can be configured toreceive user inputs for each of the new security devices through, forexample, menu controls 1834.

Referring to FIG. 18B, an example integrated control interface 1850 isprovided on the output device 1802, such as the user control device 1716and the user computing device 1718. The integrated control interface1850 can implement the integrated control interface 1782 or theintegrated control interface 1792.

The integrated control interface 1850 can include an integrated securityand automation section 1860. The integrated security and automationsection 1860 provides a blend of information from a legacy securitysystem (e.g., the existing security platform 1704) and information froma new security system (e.g., the security integration system 1702). Insome implementations, the integrated security and automation section1860 includes one or more subsections, such as an overall security alarmstatus subsection 1862, a device list and status subsection 1864, and azone information subsection 1866. The subsections 1862, 1864, and 1866can show a mix of information about the legacy security devices 1820(e.g., the existing devices 1727) and the new security and automationdevices 1830 (e.g., the peripheral devices 1730).

For example, the overall security alarm status subsection 1862 shows alegacy security device 1820 (“Alarm”), a status 1822 of the device, anda menu control 1824 for receiving a user input for controlling thedevice 1820. In addition or alternatively, the overall security alarmstatus subsection 1862 can show a new security device (e.g., a new alarmsystem connected to the security communicator device), a status of thedevice, and a menu control for receiving a user input for controllingthe device. Further, the device list and status subsection 1864 shows alist of one or more legacy security devices 1820 (“Front Door,” “Window(Room1),” etc.) and one or more new security and automation devices 1830(“Front Door Motion,” “Front Door Light,” “Room 1 Motion,” “GarageDoor,” etc.). The device list and status subsection 1864 can furtherinclude the statuses 1822 and 1832 and the menu controls 1824 and 1834.Moreover, the zone information subsection 1866 provides informationabout one or more zones at the premises (e.g., the zones 1740) and showsa list of one or more legacy security devices 1820 (“Front Door,” etc.)and one or more new security and automation devices 1830 (“Front DoorMotion,” “Front Door Light,” “Front Door Camera,” etc.). The zoneinformation subsection 1866 can further include the statuses 1822 and1832 and the menu controls 1824 and 1834.

FIGS. 19A-19C illustrate example integrated control interfaces on outputdevices. Referring to FIG. 19A, an example integrated control interface1900 is provided on an output device 1916, such as the user controldevice 1716. The integrated control interface 1900 can implement theintegrated control interfaces 1782, 1792, 1800, and 1850.

In this example, the integrated control interface 1900 shows an alarmstatus 1902, which can be obtained from the legacy security system, andfurther shows different devices statuses, such as a status 1904 from alegacy security device (e.g., “Front Door” sensor), and a status 1906from a new security and automation device (e.g., “Front Door Motion”sensor,” “Laundry” sensor, and “Side Door” sensor).

Referring to FIG. 19B, an example integrated control interface 1920 isprovided on an output device 1916, such as the user computing device1718. The integrated control interface 1920 can implement the integratedcontrol interfaces 1782, 1792, 1800, and 1850. In this example, theintegrated control interface 1920 shows a list of legacy and/or newsecurity and automation devices 1930, their status information 1932, andinput control elements 1934 for controlling them.

Referring to FIG. 19C, an example integrated control interface 1940 isprovided on an output device 1948, such as the user computing device1718. The integrated control interface 1940 can implement the integratedcontrol interfaces 1782, 1792, 1800, and 1850. In this example, theintegrated control interface 1940 shows a legacy security alarm device1950, its status information 1952, and input control elements 1954 forcontrolling the alarm device. Further, the integrated control interface1940 shows an image or video 1960 from a surveillance camera (which maybe a legacy camera connected to the legacy security panel, or a newcamera connected to the security communicator device). Moreover, theintegrated control interface 1940 shows one or more zones 1962 at thepremises, such as the zones 1940.

Referring now to FIG. 20 , an example system 2000 is shown, including acommunicator device 2010, a touchpad 2020, a mobile device 2030, and aplurality of peripheral devices 2041, 2042, 2043. The communicatordevice 2010 is configured for connection with a legacy security platformto enhance the legacy security platform with one or more features. Forexample, communicator device 2010 may be configured to turn aconventional security panel into an integrated home-automation, alarm,and surveillance system with cellular and IP communication capabilities,and/or connection to smart home as a service platforms.

The legacy security platform (not shown in FIG. 20 ) may include acontrol panel that does not include one or more of Z-Wavehome-automation, interactive services, IP connectivity, and/or cellularcommunications capabilities, and/or is incompatible with one or moreperipheral devices 2041, 2042, 2043. The communicator device 2010 may beconfigured to connect to the legacy control panel's keypad bus. In anexample embodiment, the communicator device 2010 is at least partiallyself-programming. For example, the communicator device 2010 may beconfigured to automatically detect a type of security panel, or featuresand functionality of a security panel, to which it is connected.Automatic detection may facilitate installation with the legacy securityplatform.

In an example embodiment, communicator device 2010 includes a pluralityof communication interfaces. For example, the communicator device 2010includes a wireless communication interface 2001 (e.g., Wi-Fi), anEthernet communication interface 2002, and a cellular communicationinterface 2003 (e.g., 4G/LTE, CAT M1 for 5F transition, etc.). Thecommunicator device 2010 may thus be described as capable of providingtriple-path cloud connectivity. Communicator device may communicatealarm or home-automation events, or other communications, via one ormore of the communication interfaces. For example, the communicatordevice may select the lowest-cost communication path (e.g., wirelesscommunication interface 2001). Alternatively or additionally, thecommunicator device 2010 may select a communication path based onavailable bandwidth, such as where a particular communication path isunavailable, or for a communication having particular bandwidthrequirements. In an example embodiment, the communicator device 2010 mayautomatically select a particular communication path, or switch betweencommunication paths, promoting reliable and robust communication.

System 2000 includes one or more peripheral devices 2041, 2042, 2043.Peripheral devices 2041, 2042, 2043 may include automated locks,thermostats, lights, garage door controllers, sensors, other devices. Insome embodiments, one or more peripheral devices 2041, 2042, 2043 werenot part of the legacy security platform (e.g., were integrated withsystem 2000 after communicator 2010 was connected), and/or are notcompatible with the legacy security panel. Communicator device 2010 isconfigured to operate with peripheral devices 2041, 2042, 2043, suchthat the peripheral devices 2041, 2042, 2043 can be used in system 2000to enhance its functionality. In an example embodiment, communicatordevice 2010 provides local network and remote connectivity usingwireless communication interface 2001 (e.g., Wi-Fi), which canfacilitate addition of peripheral devices 2041, 2042, 2043 to system2000.

In some embodiments, the communicator device 2010 is configured tocommunicate using proprietary communication protocols. For example, thecommunicator device 2010 may communicate with proprietary encryptedsecurity sensors. One or more peripheral devices 2041, 2042, 2043, forexample, that include proprietary encrypted security sensors, may beadded to system 2000. In some example embodiments, the communicatordevice 2010 may include a translator 2005 to facilitate communicationwith the proprietary encrypted security sensors.

In an example embodiment, communicator device 2010 facilitates videoviewing of local cameras 2041, 2042 over a home network connection, suchas a shared network between communicator device 2010 and local cameras2041, 2042.

In an example embodiment, system 2000 is configured to provide an arrayof security and automation features in a single, unified user interface.The communicator device 2010 can facilitate replacement of conventionalkeypads (e.g., with physical buttons) with large-display touchpads.Doing so can improve the user experience and facilitate efficientprogramming and monitoring of the system 2000. Additionally, thetouchpad 2020 can provide a unified user experience between use insidethe premises (e.g., on touchpad 2020) and outside the premises (e.g., ona mobile application of mobile device 2030). In an example embodiment, aconsistent user interface is provided on both the touchpad 2020 and oneor more mobile devices 2030. Moreover, the user interface of touchpad2020 and mobile device 2030 may display security, surveillance, and homeautomation features simultaneously on the display. In some embodiments,touchpad 2020 and mobile device 2030 may each be configured to display auser-specific dashboard with integrated video (e.g., from a surveillancecamera 2042, 2043) home automation (e.g., front door sensor), andsecurity services on a single page for simultaneous viewing by a user.

In an example embodiment, the communicator device 2010 creates adedicated local network to communicate with local devices (e.g., localIP devices), such as touchpad 2020.

In an example embodiment, all sensor data (e.g., anything with a contactID), may be incorporated with the communicator device for alarm eventsand home-automation events, for example.

In some embodiments, the communicator device 2010 allows local networkconnections to be configured over a cellular communication path with thecommunicator device 2010. The system 2000 may thus be remotely managed.A communicator device 2010 that facilitate remote management can reducethe need to dispatch a installer/truck to a premises. For example, Wi-Ficredentials can be remotely managed and changed over the cellularnetwork so that the communicator device 2010 can be reconnected to theWi-Fi network without dispatching an installer/truck. Alternatively oradditionally, other system configurations may be remotely selected orupdated.

FIG. 21 depicts an example system 2100 within which the communicatordevice 2010 is configured to provide the services and features describedthroughout this document. The system 2100 can be similar to the system2000 described above with regard to FIG. 20 .

In the depicted example, the communicator device 2010 is configured tocommunicate with a variety of peripheral devices using a variety ofcommunication protocols, standards, and communication interfaces (2140).For example, the communicator device 2010 is configured to communicatewith cameras, such as cameras that include object detection, facialrecognition features, and/or other image-based analysis andidentification features. The communicator device 2010 is also configuredto communicate securely with activity monitoring sensors and/or othersensors, such as through encrypted, obfuscated, and/or other securedcommunication techniques. Such sensors can include, for example,personal monitored devices, new security monitored devices (e.g.,security monitored devices enrolled with the communicator device 2010separately from an existing/separate security panel, such as a legacysecurity panel), new IoT sensors (e.g., IoT sensors enrolled with thecommunicator device 2010 separately from an existing/separate IoThub/device), and/or other sensors/devices. The communicator device 2010is also configured to communicate with various devices, sensors, andsystems using industry standard protocols and devices, such ascommunications via BLUETOOTH, Wi-Fi, Z-wave, and/or others. Thecommunicator device 2010 is also configured to communicate with voiceand/or graphical peripherals, such as smart speaker devices (e.g.,AMAZON ALEXA, GOOGLE HOME). In some instances, the communicator device2010 provides authentication and/or control of various operations on thecommunicator device 2010 and/or connected systems (e.g., connectedsecurity panels, connected home automation panels, connected IoT hubs)via communication with voice and/or graphical peripherals, cameras withobject detection and/or other detection features (e.g., facialrecognition features), and/or others of the connected devices.

The communicator device 2010 is configured to communicate with a cloudbased computer system 2120 via one or more communication networks 2110,such as over one or more IP networks (e.g., Ethernet, Wi-Fi, and/orother IP networks) and/or cellular networks (e.g., 4G LTE, 5G IoT,and/or other cellular networks).

The cloud based computer system 2120 can provide various services 2130related to the communicator device 2010, such as real-time and/or nearreal-time data and control access, multipath notification alternatives,multiple service enablement, and/or other services. The services 2130can be provided to a user across any of a variety of devices, such asthe touchpad 2020, the mobile device 2030, and/or other user devices.The services 2130 can be provided to such devices when they are localand/or remote from the premises where the communicator device 2010 islocated.

FIG. 22 is depicts an example system 2200 with a more detailed view ofthe components of the communicator device 2010. The example system 2200can be similar to the systems 2000 and/or 2100 described above withregard to FIGS. 20 and 21 , respectively.

In the depicted example, the communicator device 2010 includes anEthernet port 2220, a Wi-Fi/BTLE processor 2230, a processor 2240, aninterface 2250 to connect with security and/or automation systems (e.g.,Vista, Concord, DSC, Networx, Simon, Napco-Legacy Panel, and/or others),and/or a cellular radio 2260. The communicator device 2010 canoptionally include a sensor radio 2270, which can enable sensors toeither be enrolled into the panel the communicator device 2010 isattached to via the interface 2250, or alternatively be monitoredthrough the cloud platform (2120) independent of any monitored securityoffering. This can allow consumers having systems upgraded to includethe communicator device 2010 to add a sensor that can be monitoredwithout triggering alarms on the security system. Accordingly, thecommunicator device 2010 can support an ability to add both panelmonitored and/or cloud monitored sensors to these legacy systems via theinterface 2250. The communicator device 2010 can optionally include oneor more internal options 2280 to enhance the processor 2240, such as anautomation hardware chipset/module that is optimized to communicate withand/or process automation-based information and/or a translator receiverchipset/module that is optimized to receive translator communication.The system 2200 can additionally include a touchscreen interface 2210,such as interfaces provided by the touchpad 2020, the mobile device2030, and/or other touch-based interface devices that are configured tocommunicate with the communicator device 2010.

FIG. 23 is a block diagram of computing devices 2300, 2350 that may beused to implement the systems and methods described in this document, aseither a client or as a server or plurality of servers. Computing device2300 is intended to represent various forms of digital computers, suchas laptops, desktops, workstations, personal digital assistants,servers, blade servers, mainframes, and other appropriate computers.Computing device 2350 is intended to represent various forms of mobiledevices, such as personal digital assistants, cellular telephones,smartphones, and other similar computing devices. The components shownhere, their connections and relationships, and their functions, aremeant to be examples only, and are not meant to limit implementationsdescribed and/or claimed in this document.

Computing device 2300 includes a processor 2302, memory 2304, a storagedevice 2306, a high-speed interface 2308 connecting to memory 2304 andhigh-speed expansion ports 2310, and a low speed interface 2312connecting to low speed bus 2314 and storage device 2306. Each of thecomponents 2302, 2304, 2306, 2308, 2310, and 2312, are interconnectedusing various busses, and may be mounted on a common motherboard or inother manners as appropriate. The processor 2302 can processinstructions for execution within the computing device 2300, includinginstructions stored in the memory 2304 or on the storage device 2306 todisplay graphical information for a GUI on an external input/outputdevice, such as display 2316 coupled to high-speed interface 2308. Inother implementations, multiple processors and/or multiple buses may beused, as appropriate, along with multiple memories and types of memory.Also, multiple computing devices 2300 may be connected, with each deviceproviding portions of the necessary operations (e.g., as a server bank,a group of blade servers, or a multi-processor system).

The memory 2304 stores information within the computing device 2300. Inone implementation, the memory 2304 is a volatile memory unit or units.In another implementation, the memory 2304 is a non-volatile memory unitor units. The memory 2304 may also be another form of computer-readablemedium, such as a magnetic or optical disk.

The storage device 2306 is capable of providing mass storage for thecomputing device 2300. In one implementation, the storage device 2306may be or contain a computer-readable medium, such as a floppy diskdevice, a hard disk device, an optical disk device, or a tape device, aflash memory or other similar solid state memory device, or an array ofdevices, including devices in a storage area network or otherconfigurations. A computer program product can be tangibly embodied inan information carrier. The computer program product may also containinstructions that, when executed, perform one or more methods, such asthose described above. The information carrier is a computer- ormachine-readable medium, such as the memory 2304, the storage device2306, or memory on processor 2302.

The high-speed controller 2308 manages bandwidth-intensive operationsfor the computing device 2300, while the low speed controller 2312manages lower bandwidth-intensive operations. Such allocation offunctions is an example only. In one implementation, the high-speedcontroller 2308 is coupled to memory 2304, display 2316 (e.g., through agraphics processor or accelerator), and to high-speed expansion ports2310, which may accept various expansion cards (not shown). In theimplementation, low-speed controller 2312 is coupled to storage device2306 and low-speed expansion port 2314. The low-speed expansion port,which may include various communication ports (e.g., USB, Bluetooth,Ethernet, wireless Ethernet) may be coupled to one or more input/outputdevices, such as a keyboard, a pointing device, a scanner, or anetworking device such as a switch or router, e.g., through a networkadapter.

The computing device 2300 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as astandard server 2320, or multiple times in a group of such servers. Itmay also be implemented as part of a rack server system 2324. Inaddition, it may be implemented in a personal computer such as a laptopcomputer 2322. Alternatively, components from computing device 2300 maybe combined with other components in a mobile device (not shown), suchas device 2350. Each of such devices may contain one or more ofcomputing device 2300, 2350, and an entire system may be made up ofmultiple computing devices 2300, 2350 communicating with each other.

Computing device 2350 includes a processor 2352, memory 2364, aninput/output device such as a display 2354, a communication interface2366, and a transceiver 2368, among other components. The device 2350may also be provided with a storage device, such as a microdrive orother device, to provide additional storage. Each of the components2350, 2352, 2364, 2354, 2366, and 2368, are interconnected using variousbuses, and several of the components may be mounted on a commonmotherboard or in other manners as appropriate.

The processor 2352 can execute instructions within the computing device2350, including instructions stored in the memory 2364. The processormay be implemented as a chipset of chips that include separate andmultiple analog and digital processors. Additionally, the processor maybe implemented using any of a number of architectures. For example, theprocessor may be a CISC (Complex Instruction Set Computers) processor, aRISC (Reduced Instruction Set Computer) processor, or a MISC (MinimalInstruction Set Computer) processor. The processor may provide, forexample, for coordination of the other components of the device 2350,such as control of user interfaces, applications run by device 2350, andwireless communication by device 2350.

Processor 2352 may communicate with a user through control interface2358 and display interface 2356 coupled to a display 2354. The display2354 may be, for example, a TFT (Thin-Film-Transistor Liquid CrystalDisplay) display or an OLED (Organic Light Emitting Diode) display, orother appropriate display technology. The display interface 2356 maycomprise appropriate circuitry for driving the display 2354 to presentgraphical and other information to a user. The control interface 2358may receive commands from a user and convert them for submission to theprocessor 2352. In addition, an external interface 2362 may be providein communication with processor 2352, so as to enable near areacommunication of device 2350 with other devices. External interface 2362may provided, for example, for wired communication in someimplementations, or for wireless communication in other implementations,and multiple interfaces may also be used.

The memory 2364 stores information within the computing device 2350. Thememory 2364 can be implemented as one or more of a computer-readablemedium or media, a volatile memory unit or units, or a non-volatilememory unit or units. Expansion memory 2374 may also be provided andconnected to device 850 through expansion interface 2372, which mayinclude, for example, a SIMM (Single In Line Memory Module) cardinterface. Such expansion memory 2374 may provide extra storage spacefor device 2350, or may also store applications or other information fordevice 2350. Specifically, expansion memory 2374 may includeinstructions to carry out or supplement the processes described above,and may include secure information also. Thus, for example, expansionmemory 2374 may be provide as a security module for device 2350, and maybe programmed with instructions that permit secure use of device 2350.In addition, secure applications may be provided via the SIMM cards,along with additional information, such as placing identifyinginformation on the SIMM card in a non-hackable manner.

The memory may include, for example, flash memory and/or NVRAM memory,as discussed below. In one implementation, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, such as the memory 2364, expansionmemory 2374, or memory on processor 2352 that may be received, forexample, over transceiver 2368 or external interface 2362.

Device 2350 may communicate wirelessly through communication interface2366, which may include digital signal processing circuitry wherenecessary. Communication interface 2366 may provide for communicationsunder various modes or protocols, such as GSM voice calls, SMS, EMS, orMMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others.Such communication may occur, for example, through radio-frequencytransceiver 2368. In addition, short-range communication may occur, suchas using a Bluetooth, WiFi, or other such transceiver (not shown). Inaddition, GPS (Global Positioning System) receiver module 2370 mayprovide additional navigation- and location-related wireless data todevice 2350, which may be used as appropriate by applications running ondevice 2350.

Device 2350 may also communicate audibly using audio codec 2360, whichmay receive spoken information from a user and convert it to usabledigital information. Audio codec 2360 may likewise generate audiblesound for a user, such as through a speaker, e.g., in a handset ofdevice 2350. Such sound may include sound from voice telephone calls,may include recorded sound (e.g., voice messages, music files, etc.) andmay also include sound generated by applications operating on device2350.

The computing device 2350 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 2380. It may also be implemented as part of asmartphone 2382, personal digital assistant, or other similar mobiledevice.

Additionally computing device 2300 or 2350 can include Universal SerialBus (USB) flash drives. The USB flash drives may store operating systemsand other applications. The USB flash drives can include input/outputcomponents, such as a wireless transmitter or USB connector that may beinserted into a USB port of another computing device.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium”“computer-readable medium” refers to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback); and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), peer-to-peernetworks (having ad-hoc or static members), grid computinginfrastructures, and the Internet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as descriptions offeatures specific to particular implementations of particularinventions. Certain features that are described in this specification inthe context of separate implementations can also be implemented incombination in a single implementation. Conversely, various featuresthat are described in the context of a single implementation can also beimplemented in multiple implementations separately or in any suitablesub-combination. Moreover, although features may be described above asacting in certain combinations and even initially claimed as such, oneor more features from a claimed combination can in some cases be excisedfrom the combination, and the claimed combination may be directed to asub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the implementations described above should not beunderstood as requiring such separation in all implementations, and itshould be understood that the described program components and systemscan generally be integrated together in a single software product orpackaged into multiple software products.

Thus, particular implementations of the subject matter have beendescribed. Other implementations are within the scope of the followingclaims. In some cases, the actions recited in the claims can beperformed in a different order and still achieve desirable results. Inaddition, the processes depicted in the accompanying figures do notnecessarily require the particular order shown, or sequential order, toachieve desirable results. In certain implementations, multitasking andparallel processing may be advantageous.

What is claimed is:
 1. A system for providing integrated security control, the system comprising: a security cloud server; a user control device; and a security communicator device configured to communicate with the security cloud server via one or more networks, the security communicator device configured to be connected to an existing security panel at a premises and further configured to perform operations comprising: receiving a signal from the existing security panel, the signal representative of an existing device connected to the existing security panel; transmitting the signal to the security cloud server; receiving a peripheral device signal representative of a peripheral device connected to the security communicator device; transmitting the peripheral device signal to the security cloud server; receiving a control signal from the security cloud server, the control signal including information about a security action determined based on the signal and the peripheral device signal; controlling the existing security panel using the control signal; connecting to the user control device; and transmitting the control signal to the user control device, the control signal being usable to generate an integrated control interface at the user control device.
 2. The system of claim 1, wherein the operations further comprises: receiving a user input from the user control device, the user input received through the integrated control interface.
 3. The system of claim 1, wherein the integrated control interface includes a blend of information about the existing device and information about the peripheral device.
 4. The system of claim 1, wherein the user control device is a portable device.
 5. The system of claim 1, wherein the user control device is connected to the security communicator device through a local network access device.
 6. The system of claim 1, wherein controlling the existing security panel comprises: transmitting the control signal to the existing security panel, the control signal usable by the existing security panel to control the existing device.
 7. The system of claim 1, wherein the operations further comprises: controlling the peripheral device based on the control signal.
 8. The system of claim 1, wherein the operations further comprises: translating the signal to a modified signal, the modified signal configured to be compatible with a protocol of the security communicator device.
 9. The system of claim 1, wherein the operations further comprises: converting the control signal to a modified control signal, the modified control signal configured to be compatible with a protocol of the existing security panel.
 10. The system of claim 1, wherein the existing device and the peripheral device is arranged in a security zone being independently monitored and controlled.
 11. The system of claim 1, wherein the security communicator device is connected to one of data bus and/or telephone line of the existing security panel.
 12. The system of claim 1, wherein the networks include one or more of an Ethernet communication, a wireless communication, and a cellular communication.
 13. The system of claim 1, wherein the security communicator device includes a local area network (LAN) interface.
 14. The system of claim 1, wherein the security communicator device includes a plurality of communication interfaces, the security communicator device configured to select a communication interface from the plurality of communication interfaces for connecting to the security cloud server or the user control device.
 15. The system of claim 14, wherein the security communicator device is configured to communicate at least one of security events, alarms, or home automation events to the security cloud server or the user control device via the selected communication interface.
 16. The system of claim 14, wherein the security communicator device is configured to select a communication interface based on at least one of availability, quality, speed, or cost of utilizing a communication path associated with the communication interface.
 17. The system of claim 14, wherein the security communicator device is configured to select an available communication interface to maintain a connection to the security cloud server.
 18. The system of claim 1, wherein the existing device connected to the existing security panel is a sensor.
 19. The system of claim 1, wherein the security communicator device is wirelessly connected to the existing security panel.
 20. The system of claim 1, wherein the peripheral device connected to the security communicator device is one of an automated lock, alarm, motion detector, lighting, security camera, glass break detector, thermostat, or garage door controller. 